Hello Klaus,
Getting the TransactionManager from an app-client is not yet supported.
It is not required by the J2EE spec but the spec doesn't forbid
supporting it either. However, if we implement it and you use it, it
will potentially not be portable to other J2EE servers.
It's also generally a bad idea to do transaction demarcation from the
client, since you want your transactions to be short. Network latency
makes the transaction much longer than it would need to be if a session
bean controlled it.
So it's not implemented, it's a portability problem and it's a
performance/stability problem, so I would try to do it in some other
way.
Regards,
Karl Avedal
Klaus Thiele wrote:
> Hello,
>
> i'm using transactions within servlets, sessionbeans
> with no problems.
>
> now i'm trying this from an ordinary app-client but it
> caught an exception:
> "java:comp/UserTransaction not found"
>
> what goes wrong?
>
> thanks a lot
> klaus
>
> import javax.naming.*;
> import javax.transaction.*;
> ...
> TransactionManager tm =
> (TransactionManager)new
> InitialContext().lookup("java:comp/UserTransaction");
>
> --
> Klaus Thiele - Personal & Informatik AG
> mailto:[EMAIL PROTECTED]
>
> "There's got to be more to life than compile-and-go."
