[jboss-user] [JBoss Seam] - Re: Nested conversations and transaction management
do-not-reply at jboss.com
Tue May 1 17:07:50 EDT 2007
Now I am really confused.
First of all let me update the sample code.
| public class ABean implements Serializable, A
| private EntityManager em;
| @In(create = true)
| @Out(required = false)
| A a; // A entity bean
| public String cancel()
| return "/AList.xhtml";
| public String initCreate()
| a = new A();
| return "/A.xhtml";
| public String processCreate()
| a = em.merge(a);
| return "/ListA.xhtml";
I have traced what happens at database level and I discovered that the database transaction is started at the merge statement and committed after that the method is ended. I presumed at the end of the conversation.
SURPRISE - SURPRISE !!!
I removed @End(beforeRedirect=true) from the processCreate() method.
The database transaction is STILL started at the merge statement and STILL committed after that the method is ended.
What is going on ? I thought that using a long-running conversation I was able to manage more http requests before actually write to the database and I thought that the database transaction was committed only at the end of the method annotated with @End.
Probably I am wrong !
Please, can anyone explain to me which is the relationship between conversation and transaction ? Is this stuff documented somewhere ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042245#4042245
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042245
More information about the jboss-user