You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by COURTAULT Francois <fr...@thalesgroup.com> on 2019/11/13 11:35:37 UTC
TomEE GraalVM native image
Hello everyone,
I am able to see some initiatives around GraalVM native-image like Quarkus, Helidon,...
I have also seen that Tomcat 9.0.26 could be built as a native image: http://tomcat.apache.org/tomcat-9.0-doc/graal.html
Digging on the web, I discover some work on TomEE side as well: https://github.com/tomitribe/graalvm-microprofile
Are you working on a TomEE version which can be built as a GraalVM native image ?
I think it should be a quite important topic to consider in the roadmap, right ?
Best Regards.
________________________________
This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.
Re: TomEE GraalVM native image
Posted by Roberto Cortez <ra...@yahoo.com.INVALID>.
GraalVM in JVM mode is still Hotspot with the GraalVM JIT compiler.
I would say that you should run some performance tests before doing the switch. In same workloads Graal JIT compiler performs better, some other cases Hotspot JIT compiler is better.
> On 13 Nov 2019, at 15:14, Richard Monson-Haefel <mo...@gmail.com> wrote:
>
> Thanks, Roberto! So, compiling with it is probably not going to be a
> priority, but running TomEE on it could be. I wonder if the
> performance advantages of using GraalVM over JVM is significant.
>
> On Wed, Nov 13, 2019 at 8:46 AM Roberto Cortez <ra...@yahoo.com.invalid>
> wrote:
>
>> Hi,
>>
>> Let me clarify that this repo:
>> https://github.com/tomitribe/graalvm-microprofile <
>> https://github.com/tomitribe/graalvm-microprofile>
>>
>> Is just to play around with the polyglot features of GraalVM.
>>
>> Building TomEE native images will be another story. I did try that when I
>> was playing with the other repo and there are a lot of things that fail.
>> This is not only about TomEE, but also about all the libraries used in
>> TomEE itself.
>>
>> To be able to build to native image, you would need to comply with
>> Substrate VM limitations stated here:
>> https://github.com/oracle/graal/blob/master/substratevm/LIMITATIONS.md <
>> https://github.com/oracle/graal/blob/master/substratevm/LIMITATIONS.md>
>>
>> For instance, projects like Quarkus or Micronaut removed all reflection
>> calls and resolve these at compile time rather than runtime. While it is
>> possible to instruct GraalVM about some reflection usage when doing the
>> native image, I believe it won’t be enough in TomEE case and most likely
>> some portions would need to be reimplemented. I have no idea what would be
>> the effort involved in a task like this. It is not trivial.
>>
>> Cheers,
>> Roberto
>>
>>> On 13 Nov 2019, at 12:55, Richard Monson-Haefel <mo...@gmail.com>
>> wrote:
>>>
>>> Hi!
>>>
>>> That would be cool. If memory serves there may be some issues with
>>> reflection and complication but running TomEE on GraalVM should work
>> since
>>> it won't try to compile the reflection stuff. I haven't run it on
>> GraalVM
>>> myself, but this would be a really cool effort and if you can get it to
>>> work it would be an awesome addition to the project in my opinion. Are
>> you
>>> interested in testing it out and working on it?
>>>
>>> Richard
>>>
>>> On Wed, Nov 13, 2019 at 5:35 AM COURTAULT Francois <
>>> francois.courtault@thalesgroup.com> wrote:
>>>
>>>> Hello everyone,
>>>>
>>>> I am able to see some initiatives around GraalVM native-image like
>>>> Quarkus, Helidon,...
>>>> I have also seen that Tomcat 9.0.26 could be built as a native image:
>>>> http://tomcat.apache.org/tomcat-9.0-doc/graal.html
>>>>
>>>> Digging on the web, I discover some work on TomEE side as well:
>>>> https://github.com/tomitribe/graalvm-microprofile
>>>>
>>>> Are you working on a TomEE version which can be built as a GraalVM
>> native
>>>> image ?
>>>> I think it should be a quite important topic to consider in the roadmap,
>>>> right ?
>>>>
>>>> Best Regards.
>>>>
>>>>
>>>>
>>>> ________________________________
>>>> This message and any attachments are intended solely for the addressees
>>>> and may contain confidential information. Any unauthorized use or
>>>> disclosure, either whole or partial, is prohibited.
>>>> E-mails are susceptible to alteration. Our company shall not be liable
>> for
>>>> the message if altered, changed or falsified. If you are not the
>> intended
>>>> recipient of this message, please delete it and notify the sender.
>>>> Although all reasonable efforts have been made to keep this transmission
>>>> free from viruses, the sender will not be liable for damages caused by a
>>>> transmitted virus.
>>>>
>>>
>>>
>>> --
>>> Richard Monson-Haefel
>>> https://twitter.com/rmonson
>>> https://www.linkedin.com/in/monsonhaefel/
>>
>>
>
> --
> Richard Monson-Haefel
> https://twitter.com/rmonson
> https://www.linkedin.com/in/monsonhaefel/
Re: TomEE GraalVM native image
Posted by Roberto Cortez <ra...@yahoo.com.INVALID>.
GraalVM in JVM mode is still Hotspot with the GraalVM JIT compiler.
I would say that you should run some performance tests before doing the switch. In same workloads Graal JIT compiler performs better, some other cases Hotspot JIT compiler is better.
> On 13 Nov 2019, at 15:14, Richard Monson-Haefel <mo...@gmail.com> wrote:
>
> Thanks, Roberto! So, compiling with it is probably not going to be a
> priority, but running TomEE on it could be. I wonder if the
> performance advantages of using GraalVM over JVM is significant.
>
> On Wed, Nov 13, 2019 at 8:46 AM Roberto Cortez <ra...@yahoo.com.invalid>
> wrote:
>
>> Hi,
>>
>> Let me clarify that this repo:
>> https://github.com/tomitribe/graalvm-microprofile <
>> https://github.com/tomitribe/graalvm-microprofile>
>>
>> Is just to play around with the polyglot features of GraalVM.
>>
>> Building TomEE native images will be another story. I did try that when I
>> was playing with the other repo and there are a lot of things that fail.
>> This is not only about TomEE, but also about all the libraries used in
>> TomEE itself.
>>
>> To be able to build to native image, you would need to comply with
>> Substrate VM limitations stated here:
>> https://github.com/oracle/graal/blob/master/substratevm/LIMITATIONS.md <
>> https://github.com/oracle/graal/blob/master/substratevm/LIMITATIONS.md>
>>
>> For instance, projects like Quarkus or Micronaut removed all reflection
>> calls and resolve these at compile time rather than runtime. While it is
>> possible to instruct GraalVM about some reflection usage when doing the
>> native image, I believe it won’t be enough in TomEE case and most likely
>> some portions would need to be reimplemented. I have no idea what would be
>> the effort involved in a task like this. It is not trivial.
>>
>> Cheers,
>> Roberto
>>
>>> On 13 Nov 2019, at 12:55, Richard Monson-Haefel <mo...@gmail.com>
>> wrote:
>>>
>>> Hi!
>>>
>>> That would be cool. If memory serves there may be some issues with
>>> reflection and complication but running TomEE on GraalVM should work
>> since
>>> it won't try to compile the reflection stuff. I haven't run it on
>> GraalVM
>>> myself, but this would be a really cool effort and if you can get it to
>>> work it would be an awesome addition to the project in my opinion. Are
>> you
>>> interested in testing it out and working on it?
>>>
>>> Richard
>>>
>>> On Wed, Nov 13, 2019 at 5:35 AM COURTAULT Francois <
>>> francois.courtault@thalesgroup.com> wrote:
>>>
>>>> Hello everyone,
>>>>
>>>> I am able to see some initiatives around GraalVM native-image like
>>>> Quarkus, Helidon,...
>>>> I have also seen that Tomcat 9.0.26 could be built as a native image:
>>>> http://tomcat.apache.org/tomcat-9.0-doc/graal.html
>>>>
>>>> Digging on the web, I discover some work on TomEE side as well:
>>>> https://github.com/tomitribe/graalvm-microprofile
>>>>
>>>> Are you working on a TomEE version which can be built as a GraalVM
>> native
>>>> image ?
>>>> I think it should be a quite important topic to consider in the roadmap,
>>>> right ?
>>>>
>>>> Best Regards.
>>>>
>>>>
>>>>
>>>> ________________________________
>>>> This message and any attachments are intended solely for the addressees
>>>> and may contain confidential information. Any unauthorized use or
>>>> disclosure, either whole or partial, is prohibited.
>>>> E-mails are susceptible to alteration. Our company shall not be liable
>> for
>>>> the message if altered, changed or falsified. If you are not the
>> intended
>>>> recipient of this message, please delete it and notify the sender.
>>>> Although all reasonable efforts have been made to keep this transmission
>>>> free from viruses, the sender will not be liable for damages caused by a
>>>> transmitted virus.
>>>>
>>>
>>>
>>> --
>>> Richard Monson-Haefel
>>> https://twitter.com/rmonson
>>> https://www.linkedin.com/in/monsonhaefel/
>>
>>
>
> --
> Richard Monson-Haefel
> https://twitter.com/rmonson
> https://www.linkedin.com/in/monsonhaefel/
Re: TomEE GraalVM native image
Posted by Richard Monson-Haefel <mo...@gmail.com>.
Thanks, Roberto! So, compiling with it is probably not going to be a
priority, but running TomEE on it could be. I wonder if the
performance advantages of using GraalVM over JVM is significant.
On Wed, Nov 13, 2019 at 8:46 AM Roberto Cortez <ra...@yahoo.com.invalid>
wrote:
> Hi,
>
> Let me clarify that this repo:
> https://github.com/tomitribe/graalvm-microprofile <
> https://github.com/tomitribe/graalvm-microprofile>
>
> Is just to play around with the polyglot features of GraalVM.
>
> Building TomEE native images will be another story. I did try that when I
> was playing with the other repo and there are a lot of things that fail.
> This is not only about TomEE, but also about all the libraries used in
> TomEE itself.
>
> To be able to build to native image, you would need to comply with
> Substrate VM limitations stated here:
> https://github.com/oracle/graal/blob/master/substratevm/LIMITATIONS.md <
> https://github.com/oracle/graal/blob/master/substratevm/LIMITATIONS.md>
>
> For instance, projects like Quarkus or Micronaut removed all reflection
> calls and resolve these at compile time rather than runtime. While it is
> possible to instruct GraalVM about some reflection usage when doing the
> native image, I believe it won’t be enough in TomEE case and most likely
> some portions would need to be reimplemented. I have no idea what would be
> the effort involved in a task like this. It is not trivial.
>
> Cheers,
> Roberto
>
> > On 13 Nov 2019, at 12:55, Richard Monson-Haefel <mo...@gmail.com>
> wrote:
> >
> > Hi!
> >
> > That would be cool. If memory serves there may be some issues with
> > reflection and complication but running TomEE on GraalVM should work
> since
> > it won't try to compile the reflection stuff. I haven't run it on
> GraalVM
> > myself, but this would be a really cool effort and if you can get it to
> > work it would be an awesome addition to the project in my opinion. Are
> you
> > interested in testing it out and working on it?
> >
> > Richard
> >
> > On Wed, Nov 13, 2019 at 5:35 AM COURTAULT Francois <
> > francois.courtault@thalesgroup.com> wrote:
> >
> >> Hello everyone,
> >>
> >> I am able to see some initiatives around GraalVM native-image like
> >> Quarkus, Helidon,...
> >> I have also seen that Tomcat 9.0.26 could be built as a native image:
> >> http://tomcat.apache.org/tomcat-9.0-doc/graal.html
> >>
> >> Digging on the web, I discover some work on TomEE side as well:
> >> https://github.com/tomitribe/graalvm-microprofile
> >>
> >> Are you working on a TomEE version which can be built as a GraalVM
> native
> >> image ?
> >> I think it should be a quite important topic to consider in the roadmap,
> >> right ?
> >>
> >> Best Regards.
> >>
> >>
> >>
> >> ________________________________
> >> This message and any attachments are intended solely for the addressees
> >> and may contain confidential information. Any unauthorized use or
> >> disclosure, either whole or partial, is prohibited.
> >> E-mails are susceptible to alteration. Our company shall not be liable
> for
> >> the message if altered, changed or falsified. If you are not the
> intended
> >> recipient of this message, please delete it and notify the sender.
> >> Although all reasonable efforts have been made to keep this transmission
> >> free from viruses, the sender will not be liable for damages caused by a
> >> transmitted virus.
> >>
> >
> >
> > --
> > Richard Monson-Haefel
> > https://twitter.com/rmonson
> > https://www.linkedin.com/in/monsonhaefel/
>
>
--
Richard Monson-Haefel
https://twitter.com/rmonson
https://www.linkedin.com/in/monsonhaefel/
Re: TomEE GraalVM native image
Posted by Richard Monson-Haefel <mo...@gmail.com>.
Thanks, Roberto! So, compiling with it is probably not going to be a
priority, but running TomEE on it could be. I wonder if the
performance advantages of using GraalVM over JVM is significant.
On Wed, Nov 13, 2019 at 8:46 AM Roberto Cortez <ra...@yahoo.com.invalid>
wrote:
> Hi,
>
> Let me clarify that this repo:
> https://github.com/tomitribe/graalvm-microprofile <
> https://github.com/tomitribe/graalvm-microprofile>
>
> Is just to play around with the polyglot features of GraalVM.
>
> Building TomEE native images will be another story. I did try that when I
> was playing with the other repo and there are a lot of things that fail.
> This is not only about TomEE, but also about all the libraries used in
> TomEE itself.
>
> To be able to build to native image, you would need to comply with
> Substrate VM limitations stated here:
> https://github.com/oracle/graal/blob/master/substratevm/LIMITATIONS.md <
> https://github.com/oracle/graal/blob/master/substratevm/LIMITATIONS.md>
>
> For instance, projects like Quarkus or Micronaut removed all reflection
> calls and resolve these at compile time rather than runtime. While it is
> possible to instruct GraalVM about some reflection usage when doing the
> native image, I believe it won’t be enough in TomEE case and most likely
> some portions would need to be reimplemented. I have no idea what would be
> the effort involved in a task like this. It is not trivial.
>
> Cheers,
> Roberto
>
> > On 13 Nov 2019, at 12:55, Richard Monson-Haefel <mo...@gmail.com>
> wrote:
> >
> > Hi!
> >
> > That would be cool. If memory serves there may be some issues with
> > reflection and complication but running TomEE on GraalVM should work
> since
> > it won't try to compile the reflection stuff. I haven't run it on
> GraalVM
> > myself, but this would be a really cool effort and if you can get it to
> > work it would be an awesome addition to the project in my opinion. Are
> you
> > interested in testing it out and working on it?
> >
> > Richard
> >
> > On Wed, Nov 13, 2019 at 5:35 AM COURTAULT Francois <
> > francois.courtault@thalesgroup.com> wrote:
> >
> >> Hello everyone,
> >>
> >> I am able to see some initiatives around GraalVM native-image like
> >> Quarkus, Helidon,...
> >> I have also seen that Tomcat 9.0.26 could be built as a native image:
> >> http://tomcat.apache.org/tomcat-9.0-doc/graal.html
> >>
> >> Digging on the web, I discover some work on TomEE side as well:
> >> https://github.com/tomitribe/graalvm-microprofile
> >>
> >> Are you working on a TomEE version which can be built as a GraalVM
> native
> >> image ?
> >> I think it should be a quite important topic to consider in the roadmap,
> >> right ?
> >>
> >> Best Regards.
> >>
> >>
> >>
> >> ________________________________
> >> This message and any attachments are intended solely for the addressees
> >> and may contain confidential information. Any unauthorized use or
> >> disclosure, either whole or partial, is prohibited.
> >> E-mails are susceptible to alteration. Our company shall not be liable
> for
> >> the message if altered, changed or falsified. If you are not the
> intended
> >> recipient of this message, please delete it and notify the sender.
> >> Although all reasonable efforts have been made to keep this transmission
> >> free from viruses, the sender will not be liable for damages caused by a
> >> transmitted virus.
> >>
> >
> >
> > --
> > Richard Monson-Haefel
> > https://twitter.com/rmonson
> > https://www.linkedin.com/in/monsonhaefel/
>
>
--
Richard Monson-Haefel
https://twitter.com/rmonson
https://www.linkedin.com/in/monsonhaefel/
Re: TomEE GraalVM native image
Posted by Roberto Cortez <ra...@yahoo.com.INVALID>.
Hi,
Let me clarify that this repo:
https://github.com/tomitribe/graalvm-microprofile <https://github.com/tomitribe/graalvm-microprofile>
Is just to play around with the polyglot features of GraalVM.
Building TomEE native images will be another story. I did try that when I was playing with the other repo and there are a lot of things that fail. This is not only about TomEE, but also about all the libraries used in TomEE itself.
To be able to build to native image, you would need to comply with Substrate VM limitations stated here:
https://github.com/oracle/graal/blob/master/substratevm/LIMITATIONS.md <https://github.com/oracle/graal/blob/master/substratevm/LIMITATIONS.md>
For instance, projects like Quarkus or Micronaut removed all reflection calls and resolve these at compile time rather than runtime. While it is possible to instruct GraalVM about some reflection usage when doing the native image, I believe it won’t be enough in TomEE case and most likely some portions would need to be reimplemented. I have no idea what would be the effort involved in a task like this. It is not trivial.
Cheers,
Roberto
> On 13 Nov 2019, at 12:55, Richard Monson-Haefel <mo...@gmail.com> wrote:
>
> Hi!
>
> That would be cool. If memory serves there may be some issues with
> reflection and complication but running TomEE on GraalVM should work since
> it won't try to compile the reflection stuff. I haven't run it on GraalVM
> myself, but this would be a really cool effort and if you can get it to
> work it would be an awesome addition to the project in my opinion. Are you
> interested in testing it out and working on it?
>
> Richard
>
> On Wed, Nov 13, 2019 at 5:35 AM COURTAULT Francois <
> francois.courtault@thalesgroup.com> wrote:
>
>> Hello everyone,
>>
>> I am able to see some initiatives around GraalVM native-image like
>> Quarkus, Helidon,...
>> I have also seen that Tomcat 9.0.26 could be built as a native image:
>> http://tomcat.apache.org/tomcat-9.0-doc/graal.html
>>
>> Digging on the web, I discover some work on TomEE side as well:
>> https://github.com/tomitribe/graalvm-microprofile
>>
>> Are you working on a TomEE version which can be built as a GraalVM native
>> image ?
>> I think it should be a quite important topic to consider in the roadmap,
>> right ?
>>
>> Best Regards.
>>
>>
>>
>> ________________________________
>> This message and any attachments are intended solely for the addressees
>> and may contain confidential information. Any unauthorized use or
>> disclosure, either whole or partial, is prohibited.
>> E-mails are susceptible to alteration. Our company shall not be liable for
>> the message if altered, changed or falsified. If you are not the intended
>> recipient of this message, please delete it and notify the sender.
>> Although all reasonable efforts have been made to keep this transmission
>> free from viruses, the sender will not be liable for damages caused by a
>> transmitted virus.
>>
>
>
> --
> Richard Monson-Haefel
> https://twitter.com/rmonson
> https://www.linkedin.com/in/monsonhaefel/
Re: TomEE GraalVM native image
Posted by Roberto Cortez <ra...@yahoo.com.INVALID>.
Hi,
Let me clarify that this repo:
https://github.com/tomitribe/graalvm-microprofile <https://github.com/tomitribe/graalvm-microprofile>
Is just to play around with the polyglot features of GraalVM.
Building TomEE native images will be another story. I did try that when I was playing with the other repo and there are a lot of things that fail. This is not only about TomEE, but also about all the libraries used in TomEE itself.
To be able to build to native image, you would need to comply with Substrate VM limitations stated here:
https://github.com/oracle/graal/blob/master/substratevm/LIMITATIONS.md <https://github.com/oracle/graal/blob/master/substratevm/LIMITATIONS.md>
For instance, projects like Quarkus or Micronaut removed all reflection calls and resolve these at compile time rather than runtime. While it is possible to instruct GraalVM about some reflection usage when doing the native image, I believe it won’t be enough in TomEE case and most likely some portions would need to be reimplemented. I have no idea what would be the effort involved in a task like this. It is not trivial.
Cheers,
Roberto
> On 13 Nov 2019, at 12:55, Richard Monson-Haefel <mo...@gmail.com> wrote:
>
> Hi!
>
> That would be cool. If memory serves there may be some issues with
> reflection and complication but running TomEE on GraalVM should work since
> it won't try to compile the reflection stuff. I haven't run it on GraalVM
> myself, but this would be a really cool effort and if you can get it to
> work it would be an awesome addition to the project in my opinion. Are you
> interested in testing it out and working on it?
>
> Richard
>
> On Wed, Nov 13, 2019 at 5:35 AM COURTAULT Francois <
> francois.courtault@thalesgroup.com> wrote:
>
>> Hello everyone,
>>
>> I am able to see some initiatives around GraalVM native-image like
>> Quarkus, Helidon,...
>> I have also seen that Tomcat 9.0.26 could be built as a native image:
>> http://tomcat.apache.org/tomcat-9.0-doc/graal.html
>>
>> Digging on the web, I discover some work on TomEE side as well:
>> https://github.com/tomitribe/graalvm-microprofile
>>
>> Are you working on a TomEE version which can be built as a GraalVM native
>> image ?
>> I think it should be a quite important topic to consider in the roadmap,
>> right ?
>>
>> Best Regards.
>>
>>
>>
>> ________________________________
>> This message and any attachments are intended solely for the addressees
>> and may contain confidential information. Any unauthorized use or
>> disclosure, either whole or partial, is prohibited.
>> E-mails are susceptible to alteration. Our company shall not be liable for
>> the message if altered, changed or falsified. If you are not the intended
>> recipient of this message, please delete it and notify the sender.
>> Although all reasonable efforts have been made to keep this transmission
>> free from viruses, the sender will not be liable for damages caused by a
>> transmitted virus.
>>
>
>
> --
> Richard Monson-Haefel
> https://twitter.com/rmonson
> https://www.linkedin.com/in/monsonhaefel/
Re: TomEE GraalVM native image
Posted by Richard Monson-Haefel <mo...@gmail.com>.
Hi!
That would be cool. If memory serves there may be some issues with
reflection and complication but running TomEE on GraalVM should work since
it won't try to compile the reflection stuff. I haven't run it on GraalVM
myself, but this would be a really cool effort and if you can get it to
work it would be an awesome addition to the project in my opinion. Are you
interested in testing it out and working on it?
Richard
On Wed, Nov 13, 2019 at 5:35 AM COURTAULT Francois <
francois.courtault@thalesgroup.com> wrote:
> Hello everyone,
>
> I am able to see some initiatives around GraalVM native-image like
> Quarkus, Helidon,...
> I have also seen that Tomcat 9.0.26 could be built as a native image:
> http://tomcat.apache.org/tomcat-9.0-doc/graal.html
>
> Digging on the web, I discover some work on TomEE side as well:
> https://github.com/tomitribe/graalvm-microprofile
>
> Are you working on a TomEE version which can be built as a GraalVM native
> image ?
> I think it should be a quite important topic to consider in the roadmap,
> right ?
>
> Best Regards.
>
>
>
> ________________________________
> This message and any attachments are intended solely for the addressees
> and may contain confidential information. Any unauthorized use or
> disclosure, either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable for
> the message if altered, changed or falsified. If you are not the intended
> recipient of this message, please delete it and notify the sender.
> Although all reasonable efforts have been made to keep this transmission
> free from viruses, the sender will not be liable for damages caused by a
> transmitted virus.
>
--
Richard Monson-Haefel
https://twitter.com/rmonson
https://www.linkedin.com/in/monsonhaefel/
Re: TomEE GraalVM native image
Posted by Richard Monson-Haefel <mo...@gmail.com>.
That's really a good point, Jon!
We are so close to Jakarta EE 8 compliance it's worth focusing on that for
now and coming back to GraalVM later. However, anyone who is super pumped
about GraalVM should feel no hesitation in working that problem.
On Wed, Nov 13, 2019 at 8:35 AM Jonathan Gallimore <
jonathan.gallimore@gmail.com> wrote:
> > I think it should be a quite important topic to consider in the roadmap,
> right ?
>
> I agree its cool. What's the community take on the priority? Personally,
> I'd consider getting Jakarta EE 8 done the highest priority, behind bugs
> and security updates. I'm currently trying to finish one bug, and review 2
> PRs before getting a release out, and then I'll hopefully be back to
> Jakarta EE 8.
>
> If others want to work on GraalVM native images for TomEE, that's great and
> contributions are welcome. I'll keep plugging away at Jakarta EE 8.
>
> Jon
>
> On Wed, Nov 13, 2019 at 11:35 AM COURTAULT Francois <
> francois.courtault@thalesgroup.com> wrote:
>
> > Hello everyone,
> >
> > I am able to see some initiatives around GraalVM native-image like
> > Quarkus, Helidon,...
> > I have also seen that Tomcat 9.0.26 could be built as a native image:
> > http://tomcat.apache.org/tomcat-9.0-doc/graal.html
> >
> > Digging on the web, I discover some work on TomEE side as well:
> > https://github.com/tomitribe/graalvm-microprofile
> >
> > Are you working on a TomEE version which can be built as a GraalVM native
> > image ?
> > I think it should be a quite important topic to consider in the roadmap,
> > right ?
> >
> > Best Regards.
> >
> >
> >
> > ________________________________
> > This message and any attachments are intended solely for the addressees
> > and may contain confidential information. Any unauthorized use or
> > disclosure, either whole or partial, is prohibited.
> > E-mails are susceptible to alteration. Our company shall not be liable
> for
> > the message if altered, changed or falsified. If you are not the intended
> > recipient of this message, please delete it and notify the sender.
> > Although all reasonable efforts have been made to keep this transmission
> > free from viruses, the sender will not be liable for damages caused by a
> > transmitted virus.
> >
>
--
Richard Monson-Haefel
https://twitter.com/rmonson
https://www.linkedin.com/in/monsonhaefel/
RE: TomEE GraalVM native image
Posted by COURTAULT Francois <Fr...@gemalto.com>.
Hello everyone,
If I may, priorities by order, for projects developed in my company:
1. MP 3.x
2. Graal native image => sub-projects coordination to be compatible with GraalVM native image
3. Jakarta EE 8.0 web + JMS 2.0 compliancy
Best Regards.
From: Zowalla, Richard [mailto:richard.zowalla@hs-heilbronn.de]
Sent: jeudi 14 novembre 2019 15:15
To: users@tomee.apache.org
Cc: dev@tomee.apache.org
Subject: Re: TomEE GraalVM native image
Hi Jon,
personally, I agree with your view: +1
Richard Z
Am Donnerstag, den 14.11.2019, 09:39 +0000 schrieb Jonathan Gallimore:
If we're to roll an 8.0.1 any day now, its unlikely it'll have a
MicroProfile update, as there's a number of dependencies that get pulled in
for that functionality. We can release as often as we want/can, and there's
definitely changes since 8.0.0 that we need to get released, so I wouldn't
hold up 8.0.1 for MicroProfile updates, when we can release an 8.0.2 as
soon as those changes are in.
For clarification, I don't set the roadmap for the community. For me,
Jakarta EE 8 compliance is the priority. If others wish to work on GraalVM
or other functionality in parallel, that is cool with me. An unfortunate
reality, however, is that if everything has the same priority, effectively
you have no priorities. The danger is you'll wait longer for any of it to
show up. If GraalVM native images is your priority, I would strongly
encourage you to contribute to that work.
Jon
On Thu, Nov 14, 2019 at 8:25 AM COURTAULT Francois <
francois.courtault@thalesgroup.com <ma...@thalesgroup.com> > wrote:
Hello Jonathan,
I would also consider, as the same priority level than Jakarta EE 8
compliancy, Micro Profile compliancy.
I hope that TomEE 8.0.1 will be MP 2.2... and TomEE 8.1.x MP 3.x (3.2
specification has just been released - 3 days ago)
Is it also the roadmap you or the community have in mind ?
Best Regards.
-----Original Message-----
From: Jonathan Gallimore [mailto:jonathan.gallimore@gmail.com <ma...@gmail.com> ]
Sent: mercredi 13 novembre 2019 15:25
To: users@tomee.apache.org
Cc: dev@tomee.apache.org <ma...@tomee.apache.org>
Subject: Re: TomEE GraalVM native image
I think it should be a quite important topic to consider in the
roadmap,
right ?
I agree its cool. What's the community take on the priority? Personally,
I'd consider getting Jakarta EE 8 done the highest priority, behind bugs
and security updates. I'm currently trying to finish one bug, and review 2
PRs before getting a release out, and then I'll hopefully be back to
Jakarta EE 8.
If others want to work on GraalVM native images for TomEE, that's great
and contributions are welcome. I'll keep plugging away at Jakarta EE 8.
Jon
On Wed, Nov 13, 2019 at 11:35 AM COURTAULT Francois <
francois.courtault@thalesgroup.com <ma...@thalesgroup.com> > wrote:
Hello everyone,
I am able to see some initiatives around GraalVM native-image like
Quarkus, Helidon,...
I have also seen that Tomcat 9.0.26 could be built as a native image:
https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftomca
t.apache.org%2Ftomcat-9.0-doc%2Fgraal.html&data=02%7C01%7CFrancois
.COURTAULT%40gemalto.com%7Cc1b6794714b74a427c3008d76846c01a%7C37d0a9db
7c464096bfe31add5b495d6d%7C0%7C0%7C637092525391905126&sdata=RFGUmu
KXLWAczYRvF24TmQkiIA%2BOWh%2F86K9tCTdRXjo%3D&reserved=0
Digging on the web, I discover some work on TomEE side as well:
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith
ub.com%2Ftomitribe%2Fgraalvm-microprofile&data=02%7C01%7CFrancois.
COURTAULT%40gemalto.com%7Cc1b6794714b74a427c3008d76846c01a%7C37d0a9db7
c464096bfe31add5b495d6d%7C0%7C0%7C637092525391905126&sdata=2uu3%2F
I5b0uyFefJ3iwUN2oPs4eT%2FV0APZwb52MEoGk0%3D&reserved=0
Are you working on a TomEE version which can be built as a GraalVM
native image ?
I think it should be a quite important topic to consider in the
roadmap, right ?
Best Regards.
________________________________
This message and any attachments are intended solely for the
addressees and may contain confidential information. Any unauthorized
use or disclosure, either whole or partial, is prohibited.
E-mails are susceptible to alteration. Our company shall not be liable
for the message if altered, changed or falsified. If you are not the
intended recipient of this message, please delete it and notify the
sender.
Although all reasonable efforts have been made to keep this
transmission free from viruses, the sender will not be liable for
damages caused by a transmitted virus.
________________________________
This message and any attachments are intended solely for the addressees
and may contain confidential information. Any unauthorized use or
disclosure, either whole or partial, is prohibited.
E-mails are susceptible to alteration. Our company shall not be liable for
the message if altered, changed or falsified. If you are not the intended
recipient of this message, please delete it and notify the sender.
Although all reasonable efforts have been made to keep this transmission
free from viruses, the sender will not be liable for damages caused by a
transmitted virus.
--
Richard Zowalla, M.Sc.
Research Associate, PhD Student | Medical Informatics
Hochschule Heilbronn – University of Applied Sciences
Max-Planck-Str. 39
D-74081 Heilbronn
phone: +49 7131 504 6791
mail: richard.zowalla@hs-heilbronn.de <ma...@hs-heilbronn.de>
web: http://www.mi.hs-heilbronn.de/
Re: TomEE GraalVM native image
Posted by "Zowalla, Richard" <ri...@hs-heilbronn.de>.
Hi Jon,
personally, I agree with your view: +1
Richard Z
Am Donnerstag, den 14.11.2019, 09:39 +0000 schrieb Jonathan Gallimore:
> If we're to roll an 8.0.1 any day now, its unlikely it'll have
> aMicroProfile update, as there's a number of dependencies that get
> pulled infor that functionality. We can release as often as we
> want/can, and there'sdefinitely changes since 8.0.0 that we need to
> get released, so I wouldn'thold up 8.0.1 for MicroProfile updates,
> when we can release an 8.0.2 assoon as those changes are in.
> For clarification, I don't set the roadmap for the community. For
> me,Jakarta EE 8 compliance is the priority. If others wish to work on
> GraalVMor other functionality in parallel, that is cool with me. An
> unfortunatereality, however, is that if everything has the same
> priority, effectivelyyou have no priorities. The danger is you'll
> wait longer for any of it toshow up. If GraalVM native images is your
> priority, I would stronglyencourage you to contribute to that work.
> Jon
> On Thu, Nov 14, 2019 at 8:25 AM COURTAULT Francois <
> francois.courtault@thalesgroup.com> wrote:
> Hello Jonathan,
> I would also consider, as the same priority level than Jakarta EE
> 8compliancy, Micro Profile compliancy.I hope that TomEE 8.0.1 will be
> MP 2.2... and TomEE 8.1.x MP 3.x (3.2specification has just been
> released - 3 days ago)
> Is it also the roadmap you or the community have in mind ?
> Best Regards.
> -----Original Message-----From: Jonathan Gallimore [mailto:
> jonathan.gallimore@gmail.com]Sent: mercredi 13 novembre 2019 15:25To:
> users@tomee.apache.orgCc:
> dev@tomee.apache.orgSubject: Re: TomEE GraalVM native image
> I think it should be a quite important topic to consider in
> theroadmap,right ?
> I agree its cool. What's the community take on the priority?
> Personally,I'd consider getting Jakarta EE 8 done the highest
> priority, behind bugsand security updates. I'm currently trying to
> finish one bug, and review 2PRs before getting a release out, and
> then I'll hopefully be back toJakarta EE 8.
> If others want to work on GraalVM native images for TomEE, that's
> greatand contributions are welcome. I'll keep plugging away at
> Jakarta EE 8.
> Jon
> On Wed, Nov 13, 2019 at 11:35 AM COURTAULT Francois <
> francois.courtault@thalesgroup.com> wrote:
> Hello everyone,
> I am able to see some initiatives around GraalVM native-image
> likeQuarkus, Helidon,...I have also seen that Tomcat 9.0.26 could be
> built as a native image:
> https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftomcat.apache.org%2Ftomcat-9.0-doc%2Fgraal.html&data=02%7C01%7CFrancois.COURTAULT%40gemalto.com%7Cc1b6794714b74a427c3008d76846c01a%7C37d0a9db7c464096bfe31add5b495d6d%7C0%7C0%7C637092525391905126&sdata=RFGUmuKXLWAczYRvF24TmQkiIA%2BOWh%2F86K9tCTdRXjo%3D&reserved=0
> Digging on the web, I discover some work on TomEE side as well:
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftomitribe%2Fgraalvm-microprofile&data=02%7C01%7CFrancois.COURTAULT%40gemalto.com%7Cc1b6794714b74a427c3008d76846c01a%7C37d0a9db7c464096bfe31add5b495d6d%7C0%7C0%7C637092525391905126&sdata=2uu3%2FI5b0uyFefJ3iwUN2oPs4eT%2FV0APZwb52MEoGk0%3D&reserved=0
> Are you working on a TomEE version which can be built as a
> GraalVMnative image ?I think it should be a quite important topic to
> consider in theroadmap, right ?
> Best Regards.
>
>
> ________________________________This message and any attachments are
> intended solely for theaddressees and may contain confidential
> information. Any unauthorizeduse or disclosure, either whole or
> partial, is prohibited.E-mails are susceptible to alteration. Our
> company shall not be liablefor the message if altered, changed or
> falsified. If you are not theintended recipient of this message,
> please delete it and notify thesender.
> Although all reasonable efforts have been made to keep
> thistransmission free from viruses, the sender will not be liable
> fordamages caused by a transmitted virus.
> ________________________________ This message and any attachments are
> intended solely for the addresseesand may contain confidential
> information. Any unauthorized use ordisclosure, either whole or
> partial, is prohibited.E-mails are susceptible to alteration. Our
> company shall not be liable forthe message if altered, changed or
> falsified. If you are not the intendedrecipient of this message,
> please delete it and notify the sender.Although all reasonable
> efforts have been made to keep this transmissionfree from viruses,
> the sender will not be liable for damages caused by atransmitted
> virus.
--
Richard Zowalla, M.Sc.Research Associate, PhD Student | Medical Informatics
Hochschule Heilbronn – University of Applied SciencesMax-Planck-Str. 39 D-74081 Heilbronn phone: +49 7131 504 6791mail: richard.zowalla@hs-heilbronn.deweb: http://www.mi.hs-heilbronn.de/
Re: TomEE GraalVM native image
Posted by "Zowalla, Richard" <ri...@hs-heilbronn.de>.
Hi Jon,
personally, I agree with your view: +1
Richard Z
Am Donnerstag, den 14.11.2019, 09:39 +0000 schrieb Jonathan Gallimore:
> If we're to roll an 8.0.1 any day now, its unlikely it'll have
> aMicroProfile update, as there's a number of dependencies that get
> pulled infor that functionality. We can release as often as we
> want/can, and there'sdefinitely changes since 8.0.0 that we need to
> get released, so I wouldn'thold up 8.0.1 for MicroProfile updates,
> when we can release an 8.0.2 assoon as those changes are in.
> For clarification, I don't set the roadmap for the community. For
> me,Jakarta EE 8 compliance is the priority. If others wish to work on
> GraalVMor other functionality in parallel, that is cool with me. An
> unfortunatereality, however, is that if everything has the same
> priority, effectivelyyou have no priorities. The danger is you'll
> wait longer for any of it toshow up. If GraalVM native images is your
> priority, I would stronglyencourage you to contribute to that work.
> Jon
> On Thu, Nov 14, 2019 at 8:25 AM COURTAULT Francois <
> francois.courtault@thalesgroup.com> wrote:
> Hello Jonathan,
> I would also consider, as the same priority level than Jakarta EE
> 8compliancy, Micro Profile compliancy.I hope that TomEE 8.0.1 will be
> MP 2.2... and TomEE 8.1.x MP 3.x (3.2specification has just been
> released - 3 days ago)
> Is it also the roadmap you or the community have in mind ?
> Best Regards.
> -----Original Message-----From: Jonathan Gallimore [mailto:
> jonathan.gallimore@gmail.com]Sent: mercredi 13 novembre 2019 15:25To:
> users@tomee.apache.orgCc:
> dev@tomee.apache.orgSubject: Re: TomEE GraalVM native image
> I think it should be a quite important topic to consider in
> theroadmap,right ?
> I agree its cool. What's the community take on the priority?
> Personally,I'd consider getting Jakarta EE 8 done the highest
> priority, behind bugsand security updates. I'm currently trying to
> finish one bug, and review 2PRs before getting a release out, and
> then I'll hopefully be back toJakarta EE 8.
> If others want to work on GraalVM native images for TomEE, that's
> greatand contributions are welcome. I'll keep plugging away at
> Jakarta EE 8.
> Jon
> On Wed, Nov 13, 2019 at 11:35 AM COURTAULT Francois <
> francois.courtault@thalesgroup.com> wrote:
> Hello everyone,
> I am able to see some initiatives around GraalVM native-image
> likeQuarkus, Helidon,...I have also seen that Tomcat 9.0.26 could be
> built as a native image:
> https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftomcat.apache.org%2Ftomcat-9.0-doc%2Fgraal.html&data=02%7C01%7CFrancois.COURTAULT%40gemalto.com%7Cc1b6794714b74a427c3008d76846c01a%7C37d0a9db7c464096bfe31add5b495d6d%7C0%7C0%7C637092525391905126&sdata=RFGUmuKXLWAczYRvF24TmQkiIA%2BOWh%2F86K9tCTdRXjo%3D&reserved=0
> Digging on the web, I discover some work on TomEE side as well:
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftomitribe%2Fgraalvm-microprofile&data=02%7C01%7CFrancois.COURTAULT%40gemalto.com%7Cc1b6794714b74a427c3008d76846c01a%7C37d0a9db7c464096bfe31add5b495d6d%7C0%7C0%7C637092525391905126&sdata=2uu3%2FI5b0uyFefJ3iwUN2oPs4eT%2FV0APZwb52MEoGk0%3D&reserved=0
> Are you working on a TomEE version which can be built as a
> GraalVMnative image ?I think it should be a quite important topic to
> consider in theroadmap, right ?
> Best Regards.
>
>
> ________________________________This message and any attachments are
> intended solely for theaddressees and may contain confidential
> information. Any unauthorizeduse or disclosure, either whole or
> partial, is prohibited.E-mails are susceptible to alteration. Our
> company shall not be liablefor the message if altered, changed or
> falsified. If you are not theintended recipient of this message,
> please delete it and notify thesender.
> Although all reasonable efforts have been made to keep
> thistransmission free from viruses, the sender will not be liable
> fordamages caused by a transmitted virus.
> ________________________________ This message and any attachments are
> intended solely for the addresseesand may contain confidential
> information. Any unauthorized use ordisclosure, either whole or
> partial, is prohibited.E-mails are susceptible to alteration. Our
> company shall not be liable forthe message if altered, changed or
> falsified. If you are not the intendedrecipient of this message,
> please delete it and notify the sender.Although all reasonable
> efforts have been made to keep this transmissionfree from viruses,
> the sender will not be liable for damages caused by atransmitted
> virus.
--
Richard Zowalla, M.Sc.Research Associate, PhD Student | Medical Informatics
Hochschule Heilbronn – University of Applied SciencesMax-Planck-Str. 39 D-74081 Heilbronn phone: +49 7131 504 6791mail: richard.zowalla@hs-heilbronn.deweb: http://www.mi.hs-heilbronn.de/
Re: TomEE GraalVM native image
Posted by Jonathan Gallimore <jo...@gmail.com>.
If we're to roll an 8.0.1 any day now, its unlikely it'll have a
MicroProfile update, as there's a number of dependencies that get pulled in
for that functionality. We can release as often as we want/can, and there's
definitely changes since 8.0.0 that we need to get released, so I wouldn't
hold up 8.0.1 for MicroProfile updates, when we can release an 8.0.2 as
soon as those changes are in.
For clarification, I don't set the roadmap for the community. For me,
Jakarta EE 8 compliance is the priority. If others wish to work on GraalVM
or other functionality in parallel, that is cool with me. An unfortunate
reality, however, is that if everything has the same priority, effectively
you have no priorities. The danger is you'll wait longer for any of it to
show up. If GraalVM native images is your priority, I would strongly
encourage you to contribute to that work.
Jon
On Thu, Nov 14, 2019 at 8:25 AM COURTAULT Francois <
francois.courtault@thalesgroup.com> wrote:
> Hello Jonathan,
>
> I would also consider, as the same priority level than Jakarta EE 8
> compliancy, Micro Profile compliancy.
> I hope that TomEE 8.0.1 will be MP 2.2... and TomEE 8.1.x MP 3.x (3.2
> specification has just been released - 3 days ago)
>
> Is it also the roadmap you or the community have in mind ?
>
> Best Regards.
>
> -----Original Message-----
> From: Jonathan Gallimore [mailto:jonathan.gallimore@gmail.com]
> Sent: mercredi 13 novembre 2019 15:25
> To: users@tomee.apache.org
> Cc: dev@tomee.apache.org
> Subject: Re: TomEE GraalVM native image
>
> > I think it should be a quite important topic to consider in the
> > roadmap,
> right ?
>
> I agree its cool. What's the community take on the priority? Personally,
> I'd consider getting Jakarta EE 8 done the highest priority, behind bugs
> and security updates. I'm currently trying to finish one bug, and review 2
> PRs before getting a release out, and then I'll hopefully be back to
> Jakarta EE 8.
>
> If others want to work on GraalVM native images for TomEE, that's great
> and contributions are welcome. I'll keep plugging away at Jakarta EE 8.
>
> Jon
>
> On Wed, Nov 13, 2019 at 11:35 AM COURTAULT Francois <
> francois.courtault@thalesgroup.com> wrote:
>
> > Hello everyone,
> >
> > I am able to see some initiatives around GraalVM native-image like
> > Quarkus, Helidon,...
> > I have also seen that Tomcat 9.0.26 could be built as a native image:
> > https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftomca
> > t.apache.org%2Ftomcat-9.0-doc%2Fgraal.html&data=02%7C01%7CFrancois
> > .COURTAULT%40gemalto.com%7Cc1b6794714b74a427c3008d76846c01a%7C37d0a9db
> > 7c464096bfe31add5b495d6d%7C0%7C0%7C637092525391905126&sdata=RFGUmu
> > KXLWAczYRvF24TmQkiIA%2BOWh%2F86K9tCTdRXjo%3D&reserved=0
> >
> > Digging on the web, I discover some work on TomEE side as well:
> > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith
> > ub.com%2Ftomitribe%2Fgraalvm-microprofile&data=02%7C01%7CFrancois.
> > COURTAULT%40gemalto.com%7Cc1b6794714b74a427c3008d76846c01a%7C37d0a9db7
> > c464096bfe31add5b495d6d%7C0%7C0%7C637092525391905126&sdata=2uu3%2F
> > I5b0uyFefJ3iwUN2oPs4eT%2FV0APZwb52MEoGk0%3D&reserved=0
> >
> > Are you working on a TomEE version which can be built as a GraalVM
> > native image ?
> > I think it should be a quite important topic to consider in the
> > roadmap, right ?
> >
> > Best Regards.
> >
> >
> >
> > ________________________________
> > This message and any attachments are intended solely for the
> > addressees and may contain confidential information. Any unauthorized
> > use or disclosure, either whole or partial, is prohibited.
> > E-mails are susceptible to alteration. Our company shall not be liable
> > for the message if altered, changed or falsified. If you are not the
> > intended recipient of this message, please delete it and notify the
> sender.
> > Although all reasonable efforts have been made to keep this
> > transmission free from viruses, the sender will not be liable for
> > damages caused by a transmitted virus.
> >
> ________________________________
> This message and any attachments are intended solely for the addressees
> and may contain confidential information. Any unauthorized use or
> disclosure, either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable for
> the message if altered, changed or falsified. If you are not the intended
> recipient of this message, please delete it and notify the sender.
> Although all reasonable efforts have been made to keep this transmission
> free from viruses, the sender will not be liable for damages caused by a
> transmitted virus.
>
Re: TomEE GraalVM native image
Posted by Jonathan Gallimore <jo...@gmail.com>.
If we're to roll an 8.0.1 any day now, its unlikely it'll have a
MicroProfile update, as there's a number of dependencies that get pulled in
for that functionality. We can release as often as we want/can, and there's
definitely changes since 8.0.0 that we need to get released, so I wouldn't
hold up 8.0.1 for MicroProfile updates, when we can release an 8.0.2 as
soon as those changes are in.
For clarification, I don't set the roadmap for the community. For me,
Jakarta EE 8 compliance is the priority. If others wish to work on GraalVM
or other functionality in parallel, that is cool with me. An unfortunate
reality, however, is that if everything has the same priority, effectively
you have no priorities. The danger is you'll wait longer for any of it to
show up. If GraalVM native images is your priority, I would strongly
encourage you to contribute to that work.
Jon
On Thu, Nov 14, 2019 at 8:25 AM COURTAULT Francois <
francois.courtault@thalesgroup.com> wrote:
> Hello Jonathan,
>
> I would also consider, as the same priority level than Jakarta EE 8
> compliancy, Micro Profile compliancy.
> I hope that TomEE 8.0.1 will be MP 2.2... and TomEE 8.1.x MP 3.x (3.2
> specification has just been released - 3 days ago)
>
> Is it also the roadmap you or the community have in mind ?
>
> Best Regards.
>
> -----Original Message-----
> From: Jonathan Gallimore [mailto:jonathan.gallimore@gmail.com]
> Sent: mercredi 13 novembre 2019 15:25
> To: users@tomee.apache.org
> Cc: dev@tomee.apache.org
> Subject: Re: TomEE GraalVM native image
>
> > I think it should be a quite important topic to consider in the
> > roadmap,
> right ?
>
> I agree its cool. What's the community take on the priority? Personally,
> I'd consider getting Jakarta EE 8 done the highest priority, behind bugs
> and security updates. I'm currently trying to finish one bug, and review 2
> PRs before getting a release out, and then I'll hopefully be back to
> Jakarta EE 8.
>
> If others want to work on GraalVM native images for TomEE, that's great
> and contributions are welcome. I'll keep plugging away at Jakarta EE 8.
>
> Jon
>
> On Wed, Nov 13, 2019 at 11:35 AM COURTAULT Francois <
> francois.courtault@thalesgroup.com> wrote:
>
> > Hello everyone,
> >
> > I am able to see some initiatives around GraalVM native-image like
> > Quarkus, Helidon,...
> > I have also seen that Tomcat 9.0.26 could be built as a native image:
> > https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftomca
> > t.apache.org%2Ftomcat-9.0-doc%2Fgraal.html&data=02%7C01%7CFrancois
> > .COURTAULT%40gemalto.com%7Cc1b6794714b74a427c3008d76846c01a%7C37d0a9db
> > 7c464096bfe31add5b495d6d%7C0%7C0%7C637092525391905126&sdata=RFGUmu
> > KXLWAczYRvF24TmQkiIA%2BOWh%2F86K9tCTdRXjo%3D&reserved=0
> >
> > Digging on the web, I discover some work on TomEE side as well:
> > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith
> > ub.com%2Ftomitribe%2Fgraalvm-microprofile&data=02%7C01%7CFrancois.
> > COURTAULT%40gemalto.com%7Cc1b6794714b74a427c3008d76846c01a%7C37d0a9db7
> > c464096bfe31add5b495d6d%7C0%7C0%7C637092525391905126&sdata=2uu3%2F
> > I5b0uyFefJ3iwUN2oPs4eT%2FV0APZwb52MEoGk0%3D&reserved=0
> >
> > Are you working on a TomEE version which can be built as a GraalVM
> > native image ?
> > I think it should be a quite important topic to consider in the
> > roadmap, right ?
> >
> > Best Regards.
> >
> >
> >
> > ________________________________
> > This message and any attachments are intended solely for the
> > addressees and may contain confidential information. Any unauthorized
> > use or disclosure, either whole or partial, is prohibited.
> > E-mails are susceptible to alteration. Our company shall not be liable
> > for the message if altered, changed or falsified. If you are not the
> > intended recipient of this message, please delete it and notify the
> sender.
> > Although all reasonable efforts have been made to keep this
> > transmission free from viruses, the sender will not be liable for
> > damages caused by a transmitted virus.
> >
> ________________________________
> This message and any attachments are intended solely for the addressees
> and may contain confidential information. Any unauthorized use or
> disclosure, either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable for
> the message if altered, changed or falsified. If you are not the intended
> recipient of this message, please delete it and notify the sender.
> Although all reasonable efforts have been made to keep this transmission
> free from viruses, the sender will not be liable for damages caused by a
> transmitted virus.
>
RE: TomEE GraalVM native image
Posted by COURTAULT Francois <fr...@thalesgroup.com>.
Hello Jonathan,
I would also consider, as the same priority level than Jakarta EE 8 compliancy, Micro Profile compliancy.
I hope that TomEE 8.0.1 will be MP 2.2... and TomEE 8.1.x MP 3.x (3.2 specification has just been released - 3 days ago)
Is it also the roadmap you or the community have in mind ?
Best Regards.
-----Original Message-----
From: Jonathan Gallimore [mailto:jonathan.gallimore@gmail.com]
Sent: mercredi 13 novembre 2019 15:25
To: users@tomee.apache.org
Cc: dev@tomee.apache.org
Subject: Re: TomEE GraalVM native image
> I think it should be a quite important topic to consider in the
> roadmap,
right ?
I agree its cool. What's the community take on the priority? Personally, I'd consider getting Jakarta EE 8 done the highest priority, behind bugs and security updates. I'm currently trying to finish one bug, and review 2 PRs before getting a release out, and then I'll hopefully be back to Jakarta EE 8.
If others want to work on GraalVM native images for TomEE, that's great and contributions are welcome. I'll keep plugging away at Jakarta EE 8.
Jon
On Wed, Nov 13, 2019 at 11:35 AM COURTAULT Francois < francois.courtault@thalesgroup.com> wrote:
> Hello everyone,
>
> I am able to see some initiatives around GraalVM native-image like
> Quarkus, Helidon,...
> I have also seen that Tomcat 9.0.26 could be built as a native image:
> https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftomca
> t.apache.org%2Ftomcat-9.0-doc%2Fgraal.html&data=02%7C01%7CFrancois
> .COURTAULT%40gemalto.com%7Cc1b6794714b74a427c3008d76846c01a%7C37d0a9db
> 7c464096bfe31add5b495d6d%7C0%7C0%7C637092525391905126&sdata=RFGUmu
> KXLWAczYRvF24TmQkiIA%2BOWh%2F86K9tCTdRXjo%3D&reserved=0
>
> Digging on the web, I discover some work on TomEE side as well:
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith
> ub.com%2Ftomitribe%2Fgraalvm-microprofile&data=02%7C01%7CFrancois.
> COURTAULT%40gemalto.com%7Cc1b6794714b74a427c3008d76846c01a%7C37d0a9db7
> c464096bfe31add5b495d6d%7C0%7C0%7C637092525391905126&sdata=2uu3%2F
> I5b0uyFefJ3iwUN2oPs4eT%2FV0APZwb52MEoGk0%3D&reserved=0
>
> Are you working on a TomEE version which can be built as a GraalVM
> native image ?
> I think it should be a quite important topic to consider in the
> roadmap, right ?
>
> Best Regards.
>
>
>
> ________________________________
> This message and any attachments are intended solely for the
> addressees and may contain confidential information. Any unauthorized
> use or disclosure, either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable
> for the message if altered, changed or falsified. If you are not the
> intended recipient of this message, please delete it and notify the sender.
> Although all reasonable efforts have been made to keep this
> transmission free from viruses, the sender will not be liable for
> damages caused by a transmitted virus.
>
________________________________
This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.
Re: TomEE GraalVM native image
Posted by Jonathan Gallimore <jo...@gmail.com>.
> I think it should be a quite important topic to consider in the roadmap,
right ?
I agree its cool. What's the community take on the priority? Personally,
I'd consider getting Jakarta EE 8 done the highest priority, behind bugs
and security updates. I'm currently trying to finish one bug, and review 2
PRs before getting a release out, and then I'll hopefully be back to
Jakarta EE 8.
If others want to work on GraalVM native images for TomEE, that's great and
contributions are welcome. I'll keep plugging away at Jakarta EE 8.
Jon
On Wed, Nov 13, 2019 at 11:35 AM COURTAULT Francois <
francois.courtault@thalesgroup.com> wrote:
> Hello everyone,
>
> I am able to see some initiatives around GraalVM native-image like
> Quarkus, Helidon,...
> I have also seen that Tomcat 9.0.26 could be built as a native image:
> http://tomcat.apache.org/tomcat-9.0-doc/graal.html
>
> Digging on the web, I discover some work on TomEE side as well:
> https://github.com/tomitribe/graalvm-microprofile
>
> Are you working on a TomEE version which can be built as a GraalVM native
> image ?
> I think it should be a quite important topic to consider in the roadmap,
> right ?
>
> Best Regards.
>
>
>
> ________________________________
> This message and any attachments are intended solely for the addressees
> and may contain confidential information. Any unauthorized use or
> disclosure, either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable for
> the message if altered, changed or falsified. If you are not the intended
> recipient of this message, please delete it and notify the sender.
> Although all reasonable efforts have been made to keep this transmission
> free from viruses, the sender will not be liable for damages caused by a
> transmitted virus.
>
Re: TomEE GraalVM native image
Posted by Richard Monson-Haefel <mo...@gmail.com>.
Hi!
That would be cool. If memory serves there may be some issues with
reflection and complication but running TomEE on GraalVM should work since
it won't try to compile the reflection stuff. I haven't run it on GraalVM
myself, but this would be a really cool effort and if you can get it to
work it would be an awesome addition to the project in my opinion. Are you
interested in testing it out and working on it?
Richard
On Wed, Nov 13, 2019 at 5:35 AM COURTAULT Francois <
francois.courtault@thalesgroup.com> wrote:
> Hello everyone,
>
> I am able to see some initiatives around GraalVM native-image like
> Quarkus, Helidon,...
> I have also seen that Tomcat 9.0.26 could be built as a native image:
> http://tomcat.apache.org/tomcat-9.0-doc/graal.html
>
> Digging on the web, I discover some work on TomEE side as well:
> https://github.com/tomitribe/graalvm-microprofile
>
> Are you working on a TomEE version which can be built as a GraalVM native
> image ?
> I think it should be a quite important topic to consider in the roadmap,
> right ?
>
> Best Regards.
>
>
>
> ________________________________
> This message and any attachments are intended solely for the addressees
> and may contain confidential information. Any unauthorized use or
> disclosure, either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable for
> the message if altered, changed or falsified. If you are not the intended
> recipient of this message, please delete it and notify the sender.
> Although all reasonable efforts have been made to keep this transmission
> free from viruses, the sender will not be liable for damages caused by a
> transmitted virus.
>
--
Richard Monson-Haefel
https://twitter.com/rmonson
https://www.linkedin.com/in/monsonhaefel/
Re: TomEE GraalVM native image
Posted by Jonathan Gallimore <jo...@gmail.com>.
> I think it should be a quite important topic to consider in the roadmap,
right ?
I agree its cool. What's the community take on the priority? Personally,
I'd consider getting Jakarta EE 8 done the highest priority, behind bugs
and security updates. I'm currently trying to finish one bug, and review 2
PRs before getting a release out, and then I'll hopefully be back to
Jakarta EE 8.
If others want to work on GraalVM native images for TomEE, that's great and
contributions are welcome. I'll keep plugging away at Jakarta EE 8.
Jon
On Wed, Nov 13, 2019 at 11:35 AM COURTAULT Francois <
francois.courtault@thalesgroup.com> wrote:
> Hello everyone,
>
> I am able to see some initiatives around GraalVM native-image like
> Quarkus, Helidon,...
> I have also seen that Tomcat 9.0.26 could be built as a native image:
> http://tomcat.apache.org/tomcat-9.0-doc/graal.html
>
> Digging on the web, I discover some work on TomEE side as well:
> https://github.com/tomitribe/graalvm-microprofile
>
> Are you working on a TomEE version which can be built as a GraalVM native
> image ?
> I think it should be a quite important topic to consider in the roadmap,
> right ?
>
> Best Regards.
>
>
>
> ________________________________
> This message and any attachments are intended solely for the addressees
> and may contain confidential information. Any unauthorized use or
> disclosure, either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable for
> the message if altered, changed or falsified. If you are not the intended
> recipient of this message, please delete it and notify the sender.
> Although all reasonable efforts have been made to keep this transmission
> free from viruses, the sender will not be liable for damages caused by a
> transmitted virus.
>