Ok we just looked at it with sebastien.
the bottom line is that the Tx from "getUserTransaction" is implemented
tx from JNDI is NYI and we are on it, some retooling in order, hang on.
marc
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Charles Crain
> Sent: Thursday, September 14, 2000 1:13 PM
> To: jBoss
> Subject: Re: [jBoss-User] UserTrasaction
>
>
> I was looking in the code for this. It appears that looking up a
> UserTransation
> with JNDI is not supported. The EJB 1.1 spec states explicitly that the
> container does not need to make the UserTransaction object
> available via JNDI to
> ALL clients, though several EJB containers do (JoNaS, WebLogic...)
>
> What I find weird is that even beans running WITHIN jBoss can't
> use JNDI to look
> up a UserTransaction object, and then control the transactions of
> other beans.
> Of couse, you can do the exact same thing by using bean-managed
> transactions and
> calling the getUserTransaction method of EJBContext.
>
> What I would like to see is the ability of services running
> within jBoss to look
> up UserTransaction objects and control transactions of beans.
> For instance,
> Servlets and JSP's running in the Tomcat service really should be
> able to get
> access to the UserTransaction object.
>
> -Charles
>
> Sean Han wrote:
>
> > Hi, everyone:
> >
> > If I want to get a UserTrasaction object from jBoss, what JNDI
> name should I
> > use in lookup() method?
> >
> > Thanks!
> >
> > Sean
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Talk to your friends online with Yahoo! Messenger.
> > http://im.yahoo.com
> >
> > --
> > --------------------------------------------------------------
> > To subscribe: [EMAIL PROTECTED]
> > To unsubscribe: [EMAIL PROTECTED]
> > Problems?: [EMAIL PROTECTED]
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
