marc fleury wrote: > > 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 True. And it could be done quite easily by disassociating the transaction from the thread at the end of an HTTP request, storing the transaction id in the HttpSession and restoring the association when a new request for this session comes in. But then you would get long-running transactions (at least when the http requests comes from a human user) where database connections are hold open and objects are locked, leading to scalability problems. For web services the transactions might be necessary. Harald _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
