Re: [jakarta.ee-community] A Composable Platform Over Profiles

[Richard Monson-Haefel <rmonson@xxxxxxxxxxxxx>]

Thanks, Arjan.   If JTA already defines CDI compatable @TransactionalScope context and a CDI compatable @Transactional interceptor than what would need to be added to the JTA specification to complete XA support in CDI?   I like the fact that JTA defines how CDI supports XA and I think that is a possible way forward where each specification defines how - if appropriate - it integrates with CDI.  I’m not sure that the Jakarta EE Core should require XA support but that’s a different debate. The important point is that CDI / JTA integration is defined in JTA.   JPA and JAX-RS should be defined the same way (and maybe they are already) as well as JMS, JNDI, etc.

On Thu, May 3, 2018 at 9:20 AM arjan tijms <arjan.tijms@xxxxxxxxx> wrote:

Hi,

On Thu, May 3, 2018 at 4:13 PM, Richard Monson-Haefel <rmonson@xxxxxxxxxxxxx> wrote:

+1 on moving transaction and other EJB added-value, must-have features to a CDI conformant archtecture.  Although I don’t know if CDI itself needs to include XA transations, an XA Transaction profile that depends on CDI for Jakarta EE is a good posibility. 

CDI itself should absolutely not include XA transactions, but it doesn't need to.

The JTA spec has defined a CDI compatible @TransactionalScope context and a CDI compatible @Transactional interceptor.

Kind regards,

Arjan

_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community

--

Richard Monson-Haefel
http://twitter.com/rmonson
http://www.tomitribe.com
http://www.tomitribe.io