When talking about a "public, portable way" to register your wrapper with
the server's TM, bear in mind that JTA is not required for EJB spec
compliance. See section 11.1.3 of the 1.1 draft:
The EJB architecture does not require the EJB Container to support
the JTS interfaces. The EJB architecture requires that the EJB Container
support the javax.transaction.UserTransaction interface defined in JTA, but
it does not require the support for the JTA resource manager and application
server interfaces.
> Larry Allen wrote:
> > P.S. By the way, it's not completely clear how the wrapper object is
> > supposed to register itself with the TM at first use. Presumably, it
> should
> > use the methods in the javax.transaction.Transaction interface, by
> > calling the method getTransaction() on the TranactionManager -- but, how
> > does it find the TransactionManager? There's no public, portable way to
> > do this ... which means that your wrapper object will have to have some
> > server-specific code in it.
>
> The TM is available under JNDI (see the JTA spec.). What is not
> specified is the JNDI-name, but that's not a big problem, and I believe
> that it is correct not to specify this.
>
> /Rickard
>
> --
> Rickard �berg
>
> Computer Science student@LiTH
> @home: +46 13 177937
> Email: [EMAIL PROTECTED]
> Homepage: http://www-und.ida.liu.se/~ricob684
>
> ==========================================================================
> =
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
