I am starting a transaction context from my client code and then proceeding to calling a method on a session bean. The session bean proceeds to start it's own transaction that it commits upon exiting the method. How can I force the session bean to use the transaction that I have already started in the client code?
My deployment descriptor has the following:
I have tried nearly all of the possible values for <trans-attribute> and I still can't get it to work. Is there a way of specifying no methods?