Marina,
2 points:
1) I know that in this case I could use container managed transaction; but this is just a test program, that I wrote to check the behavior of client-controlled transaction. That's why I simply have a call to an EJB method.
2) Actually, I think that the transaction is propagated from the client to the container. I say this because if, in the EJB, I use the MANDATORY attribute, the container does not complain. And even if the transaction was not propagated, I don't see why I would have the call to commit() hang...
[Message sent by forum member 'oliechti' (oliechti)]
http://forums.java.net/jive/thread.jspa?messageID=246419