anonymous wrote : | 1) Can you give me some reference to learn more about transactions that span HTTP requests ? |
This is extremely rare, it involves suspension of the transaction on a Java EE server. I'd rather not give you any references on this because you will certainly try it - without understanding why you (don't) need it. Forget that I even mentioned it :) anonymous wrote : | 2) Can @Begin(flushMode=MANUAL) help me ? | Of course, the unflushed persistence context can be held for several requests and is then flushed in the last request of a conversation. This is the basic conversational programming model in Seam, widely documented. anonymous wrote : | 3) Why seam has not options that let user manage the transactions as needed ? Am I using seam in the wrong way ? | Yes, you have a fuzzy picture about what system transactions are and now look for the wrong solutions. Seam and Java EE have _all_ options you need to handle transactions. Don't jump into the middle trying to use nested conversations, long-running persistence contexts, and complex EJB/transaction assemblies, without understanding the basics first. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043070#4043070 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4043070 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
