GlassFish 5.0.1 will use JTA 1.3. The current development release includes this change. We're not planning to publish new versions of the API jar files since this doesn't change the

Yes, sorry, Kevin is right. Transaction propagation is only required within a single product instance, which (depending on the architecture of the product) might involve multiple

Hi Klaus, I can’t comment about this issue, but full 100% absolutely compatibility with the Java EE specs is rare. The CTS/TCK supposedly contains a LOT of tests, but there’s always things

Hi Klaus, In section E.4.2.1.1 Transaction Requirements, there is the following statement. Liberty fully supports this "local" transaction propagation. Note that this transaction propagation

Hi, Doing some testing with Java modules, I found the Java EE 8 API has a splitted package problem on JTA. This was fixed on a JTA MR but it was done after Java EE 8 went final [1]. This is only a

Thanks for the clarification Bill. How can IBM Liberty be listed as a Java EE 7 and 8 Full Platform Compatible Implementation if it does not support transaction propagation in EJB remoting at all? Is

Yes, transaction propagation is required, but interoperability of transaction propagation between vendors is unspecified. klaus.rothert@... wrote on 08/10/2018 05:30 AM:

Hello, we recently looked into IBM Liberty as Java EE container and were very suprised to find that it does not support inbound or outbound transaction propagation. Asking our IBM contact about that

They're also linked from the Java EE Documentation page. Kevin Sutter wrote on 11/28/17 09:02 AM:

FWIW, https://javaee.github.io is an easy to remember URL for 'key' Java EE resources. --David

We have discussed this issue offline with Oracle if I remember correctly. The suggestion was to redirect the old URLs that Google, etc pick up to the new location. I believe the outcome was that this

Thanks, Ivar... Even Google couldn't find this for me...

You can find it at https://javaee.github.io/javaee-spec/javadocs/

It's here: https://javaee.github.io/javaee-spec/javadocs/ Ivar -- Java Champion, JCP EC/EG Member, EE4J PMC, JUG Leader

In the past, the javadoc for Java EE was housed on docs.oracle.com like this for Java EE 7: https://docs.oracle.com/javaee/7/api/ But, I can't find a corresponding site for Java EE 8. Thanks, Kevin

Arjan Tijms wrote on 09/19/17 01:29 PM: Some of the annotations have literals and some do not. There may be some rationale for why only some of the annotations need literals, but it

I'm not sure if there's any inconsistency, other than creating literals for the JSR 330 spec and including them in 299. Or is that what you're referring to? They're mostly used for the various

The CDI expert group didn't raise this at the platform level, and they didn't even do this consistently for their annotations, so I'm not clear on what their intent is with these

Sorry, that's not what I meant ;) What I meant was that each annotation should of course stay within their respective spec. I.e. @Transactional should of course stay in JTA. But the annotation literal

I'd say if there is an umbrella spec with these kinds of annotations then then it must be a requirement for the other specs to implement them. Otherwise, leave the annotations within the individual