EJB 3.0 Core Spec (Transaction and BMT)

On Page 342 Core EJB Specs:

If the client request is associated with a transaction T1, and the instance is not associated with a transaction, the container suspends the client抯 transaction association and invokes the method with an unspecified transaction context. The container resumes the client抯 transaction association (T1) when the method (together with any associated interceptor methods) completes. This case can never happen for a message-driven bean or for the invocation of a web service endpoint method of a stateless session bean.

Doubt:

Message driven beans can have Transaction attribute specified as Not Supported or Required. In the case of Not Supported - the above can happen?.

Also, why is not applicable for invocation of a web service endpoint method of a stateless session bean and applicable for a stateless session bean call?

Please guide,

Shivani

[937 byte] By [shivani.Eartha] at [2007-11-27 7:07:42]
# 1

Hi Shivani,

In the JMS programming model, transactions do not propagate from the message

producer to the message consumer so there is not any possibility for a transaction to propagate

into the JMS MDB's onMessage method.However, the text could actually use some qualification

since MDBs are capable of consuming other types of inbound messages through the Connector 1.5

contracts. In those cases it is possible for a transaction to propagate into the MDB.

Regarding WebServices, Java EE 5 does not require support for transaction propagation on

web service invocations.When this text was written such propagation was prohibited. That

restriction was loosened in Java EE 5 so this also needs some rewording.

--ken

ksaksa at 2007-7-12 18:59:07 > top of Java-index,Enterprise & Remote Computing,Enterprise Technologies...