I have a question about Transactions. The context is a servlet (or jsp) making calls to Jonas ans serving HTML pages. Is it possible to have a Transaction spanning several servlet/jsp pages? The question arises because, if I understood correctly how the Transactions are handled, they are attached to client threads. And we have no warranty that the same worker would be used when serving several pages. Imagine that we start a user transaction in a jsp page, and we store the userTransaction object in the servlet session. We finish the transaction in a different page. Would there not be problems if we happen to be served by different (servlet)threads each time (mixed transactions with other users)? The same applies to a stateful session bean. If we store it in the (servlet)session data, and recover it in a different servlet call, would the transaction in the bean not involve objects from different users calls in the same (servlet)thread? Maybe the question is trivial, or else I have not understood it right, but I think there are problems in the handling of "long running" transactions with this architecture in the scenario of a client with thread pooling (like a servlet runner is). Could anybody elaborate on that? ---- This list is cross-posted to two mail lists. To unsubscribe, follow the instructions below for the list you subscribed to. For objectweb.org: send email to [EMAIL PROTECTED] and include in the body of the message "unsubscribe ejb-container-group". For enhydra.org: send email to [EMAIL PROTECTED] and include in the body of the message "unsubscribe ejb-container-group".
