[cdi-dev] [JBoss JIRA] (CDI-520) 3.6. Java EE components

[ https://issues.jboss.org/browse/CDI-520?page=com.atlassian.jira.plugin.sy... ] Mark Struberg commented on CDI-520: ----------------------------------- a.) there is not _the_ EntityManager, there are in fact a few of them. E.g. the 'native' one from JPA vs the 'Facade' you get when using @PersistenceContext in EJBs. The later is really just a facade which delegates to the 'real' EM which he gets from the TransactionSynchronizationRegistry [1] (This is why the getDelegate() method exists btw). And the point is that this mapping gets basically maintained by the EJB container. b.) The EJB spec clearly says in chapter 13, esp 13.2.5 'Container-Managed Demarcation' and 13.3.3 'Enterprise Beans Using Bean-Managed Transaction Demarcation' that container-managed and bean-managed transactions are only defined for 'enterprise beans'. Please note that 'enterprise beans' are ONLY javax.ejb beans and _not_ the rest which is subsummed under the more generic term 'managed beans'. c.) there is no other spec which defines how transaction demarcation works for EE 'Managed Beans' (btw there are many different 'Managed Beans' in EE still...) I'm not saying this for fun but because I know a few containers which will blow up if you access a @PersistenceContext EntityManager without being in the call frame of any EJB. It might work for a few, but not that: "You are now leaving the portable sector" :D Feel free to get this fixed/clarified for EE-8 :) [1] http://docs.oracle.com/javaee/6/api/javax/transaction/TransactionSynchron... -- This message was sent by Atlassian JIRA (v6.3.15#6346)