rong). |> Thus, the requirement of the spec is that the web container |> ensures that a transaction is completed at the end of each |> http-request, by rolling back any non-completed transaction.
how is this supposed to make web services transactional? you should have the option to define "statefull sessions" in http see and have the transactional boundaries live beyond the invocation of http. 25c marcf |> |> This should be similar to what happens in the finally-part of |> TxInterceptorBMT.invoke for stateless session beans. | |Ok. I do not know if the web containers do this, but if |- they do not |- they use thread pooling |- a web component does not end a transaction |you should get a javax.transaction.NotSupportedException at some |time when a transaction is started, since the TM does not support |nested transactions, and the transaction would stay active and |still be associated with the reused thread. | | |Best Regards, | |Ole Husgaard. | |_______________________________________________ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
