Hello Rui,
Currently we do not support getting a UserTransaction reference from an
application client (the specification does not say that clients should have
access to it). We will probably implement it in a future release, but it will
then be Orion specific and not portable to every J2EE server. Also, it's usually
not a good choice to do transaction demarcation on the client.
I would recommend doing the transaction demarcation from a session bean. If you
want to, you can see the session bean as a part of your client logically, just
that it's residing on the server, and you can probably put the kind of logic you
want client transaction demarcation for in the session bean (but since I don't
know exactly what you're using it for, I can't say for sure...)
Regards,
Karl Avedal
Rui Gil wrote:
> Hi !
>
> I'm trying to use an UserTransaction in a client code.
> None of the usuals JNDI names work, like,
> UserTransaction utx =
> (UserTransaction)initialContext.lookup("java:comp/UserTransaction")
>
> What is the default JNDI name where the UserTransaction is bound for clients
> ?
> Do I have to include it as a resource in my application-client.xml to bind
> it to JNDI ?
> And how do I configure this ?
>
> thx for the help.
>
> Rui Gil
