I think it should dissassociate the thread. Since we need to know which threads
are associated with the transaction.
However, make sure you don't break the requirements from the spec,
e.g. the OTS spec:
anonymous wrote :
| suspend If the client thread is not associated with a transaction, a null object reference is returned. Otherwise, an object is returned that represents the transaction context currently associated with the client thread. This object can be given to the resume operation to reestablish this context in the same thread or a different thread. The scope within which this object is valid is implementation dependent; at a minimum, it must be usable by the client thread. In addition, the client thread becomes associated with no transaction. This operation is not dependent on the state of the transaction; in particular, it does not raise the TRANSACTION_ROLLEDBACK exception.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879612#3879612
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879612