If I'm not mistaken, fooling around with your transaction is forbidden if
you set transaction-type to Container. Also, getting the
TransactionManager directly this way is non-portable: the EJB spec
requires the container to provide a UserTransaction implementation in JNDI
at "javax.transaction.UserTransaction", but I don't believe (I don't want
to make an absolute proclamation without re-reading the spec) that
anything else is required to be there.
danch
On Wed, 6 Sep 2000, Sebastien Sahuc wrote:
> > Hello,
>
> > Inside a bean (which has been declared with
> > <transaction-type>Container</>, and which Container in turn has been
> > delcared with <trans-attribute>Required</>) , when I get the
> > TransactionManger through JDNI and call getTransaction on it, it returns
> > me a null value although I'm expecting a transaction object.
> > When I log the status given from the TrasactionManager, it gives me a
> > STATUS_UNKNOWN value, which doesn't confort me.
>
> Well it's not STATUS_UNKNOWN, but rather STATUS_NO_TRANSACTION, sorry.
> And the bean is a SessionBean.
> And same behavior when I change the container <trans-attribute> value to
> RequiresNew
>
> Sebastien
>
>
>
> > Could anyone give me a hint of what going on ?
>
> > Thanks,
>
> > Sebastien
>
> > PS: I did not know on which list to post the question. Forgive me if I've
> > mistaken the list.
>
--
Dan Christopherson (danch)
STR Technical Architect (www.str.com)
