p228 in HF EJB (sessionContext)

[George Fung]

ejbCreate(), ejbRemove().
For stateful bean, it can use SessionContext to get a transaction reeference and call methods on it (BMT bean).
However, it's not case for stateless bean. Do you know the reason? I think stateless bean can access BMT transaction,too. It should be mistake in the book. Am I right?

[Darien Cheung]

The EJB spec says the same thing [p90]. I find it confusing too, but I like to convince myself that because stateless SB's are not tied to client calling create(), remove() there is no meaningful transaction context when the container calls ejbCreate(), ejbRemove(). On the other hand, stateful SB's tie ejbCreate() with a client call. Not sure if this is really true but I'll use that to help me remember.

[Nishant Verma]

ejbCreate and ejbRemove runs in unspecified tx context in case of session bean. So no point calling getUserTransaction or getRollbackOnly, setRollbackOnly here.

[Nishant Verma]

Originally posted by Nishant Verma:
ejbCreate and ejbRemove runs in unspecified tx context in case of session bean. So no point calling getUserTransaction or getRollbackOnly, setRollbackOnly here.

Above methods will throw IllegalStateException. Applies to **CMT** only. However BMT session bean can start transaction in ejbCreate, ejbRemove. Because BMT EJB's dont care about the container - however smart

[George Fung]

i will use the 1st answer to help me remember ^_^