Exact dates are hard to provide. As a rough idea, we'll need a OpenJPA
probably good to go. The TomEE release can take a week or to, depending on
any issues that crop up, and allowing enough time to vote.
Hope that is some help.
Post by COURTAULT FrancoisHello Romain and Mark,
If I have understood you well, TomEE 8 will address µProfile 1.3 since
its first version.
But what about my first question regarding 7.0.5 ?
Best Regards.
-----Original Message-----
Sent: lundi 14 mai 2018 15:17
Subject: Re: TomEE Stable and OpenJDK
Le lun. 14 mai 2018 13:16, COURTAULT Francois <
Post by COURTAULT FrancoisHello Mark,
Thanks a lot for sharing the TomEE roadmap.
- java 9 and above support (java 10 and 11)
- JavaEE 8 specification support
- µProfile follow up: no TomEE µProfile released yet whereas
others exist today like Payara micro, Wildfly Swarm for example.
So first, java 9 and above support: when you say 7.0.5 in preparation
right now, could you provide us please a release date ?
Second, I have another question: TomEE 7.1.x will address µProfile
1.3, right ? So why, TomEE 8.x won't address µProfile 1.3 at starting
point ?
8 will, 7.1 is still being discussed AFAIK
The side note is you can import most of mp spec as any lib in any tomee
distro since they never really depends on the container and rely - as any
spec should - on cdi IoC for the wiring.
Post by COURTAULT FrancoisBest regards.
-----Original Message-----
Sent: dimanche 6 mai 2018 13:11
Subject: Re: TomEE Stable and OpenJDK
I'm running it in production with OpenJDK.
Actually whenever you have some RHEL server then you will run on OpenJDK.
So those days everything which is in the Linux server area will almost
certainly run perfectly fine on OpenJDK.
LieGrue,
strub
Post by Fredrik JonsonPost by Mark StrubergI think what the download page fails to communicate is which EE
level it addresses.
TomEE-1.7.x adresses the JavaEE 6 specifications, with minimum requirement
Java7 (up to Java8)
TomEE-7.0.x adresses JavaEE 7, with minimum Java7, soon up to Java11
(7.0.5 in preparation right now)
TomEE-7.1.x (wip) will address JavaEE7 + MicroProfile 1.3 with
minimum Java8 TomEE-8.0.x (wip) will address JavaEE8 + MicroProfile
1.0 with minimum Java8
Thanks for that clarification. It may seem obvious to people in the
know, but it is interesting to see a statement on the upper bound of
supported JDK/JRE version, as well as the lower bound. In addition
to the supported Java EE version range, for the major Tomee versions.
Now, just to be explicit here: Apart from EE certification, does the
Tomee community consider OpenJDK on equal footing to OracleJDK when
it comes to Tomee deployment? Is there any important reason not to
recommend OpenJDK over, or at least on par with, OracleJDK?
I'm asking because I still encounter a bit of hesitation towards
migrating from OracleJDK to OpenJDK. It would be helpful if open
source projects such as Tomee made a clear stance on OpenJDK.
BTW, I also run Tomee 7.x on OpenJDK 8, and have not found any
issues compared to OracleJDK. So, now we know there are more than
one application deployed on Tomee and OpenJDK. :)
--
Fredrik Jonson
________________________________
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.
Post by COURTAULT FrancoisAlthough 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.