I noticed this hiding when trying to use Seam Persistence with AS7, it of course fails because it can not find the TransactionManager in JNDI, having the resource available somewhere that's easily accessible needs to be done for the reason(s) Ales mentioned and for Seam as well.
On Fri, Apr 29, 2011 at 15:26, Ales Justin <[email protected]> wrote: > IMO TransactionServices should also expose TransactionManager. > > Since with AS7, which hides TM from JNDI, one cannot easily register > XAResources: > > Transaction > public boolean enlistResource(XAResource xaRes) throws RollbackException, > IllegalStateException, SystemException > > or suspending/resuming current Tx. > Specially XAResources handling is a must to be able to enlist if you're > doing some non-trivial tx-based work. > > This way the integration layer would make sure the TM is exposed as a CDI > service. > > Wdyt? > > -Ales > > > > _______________________________________________ > weld-dev mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/weld-dev > -- Jason Porter http://lightguard-jp.blogspot.com http://twitter.com/lightguardjp Software Engineer Open Source Advocate Author of Seam Catch - Next Generation Java Exception Handling PGP key id: 926CCFF5 PGP key available at: keyserver.net, pgp.mit.edu
_______________________________________________ weld-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/weld-dev
