[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1292) conversations re-started in pageflows
Andy Gibson (JIRA)
jira-events at lists.jboss.org
Fri May 4 15:13:52 EDT 2007
[ http://jira.jboss.com/jira/browse/JBSEAM-1292?page=all ]
Andy Gibson updated JBSEAM-1292:
--------------------------------
Description:
See forum post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043286#4043286
The problem is that when you use the <begin-conversation> tag in pages.xml with a pageflow. Any time the page is rendered within the pageflow, Seam attemps to re-perform the conversation requirements. (starting, joining or creating a new nested conversation).
Note, this is only a problem when using a pageflow, without a pageflow, everything runs fine.
If you use @Begin annotations on a method with a pageflow, then everything is fine.
If you use s:link with conversation and pageflow attributes, then it runs fine.
For the different attribute options, here are the results :
<begin-conversation> results in an error (beginning conversation from long running conversation) as it tries to start a new conversation
<begin-conversation join="true"> works ok because it just joins the conversation it started first time it hit the page
<begin-conversation nested="true"> causes a new nested conversation to be created each time the page is rendered
Somewhat similar to issue http://jira.jboss.org/jira/browse/JBSEAM-608 which was related to the pageflow re-starting on each render, except now it is the conversation that is trying to re-start on each render.
At the end of my attached forum post, I describe why using just join=true is not a practical solution for more complex scenarios involving nested flows, and additionally, it makes nested flows impossible to use from pages.xml.
was:
See forum post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043286#4043286
The problem is that when you use the <begin-conversation> tag in pages.xml with a pageflow, any time the page is rendered Seam attemps to re-perform the conversation requirements. (starting, joining or creating a new nested one).
Note, this is ONLY a problem when using a pageflow, without a pageflow, everything runs fine.
If you use @Begin annotations on a method with a pageflow, then everything is fine.
It appears to only be when using begin-conversation in pages.xml with a pageflow.
For the difference options, here are the results :
<begin-conversation> results in an error (beginning conversation from long running conversation)
<begin-conversation join="true"> works ok because it just joins the conversation it started first time it hit the page
<begin-conversation nested="true"> causes a new nested conversation to be created each time the page is rendered
Somewhat similar to issue http://jira.jboss.org/jira/browse/JBSEAM-608 which was related to the pageflow re-starting on each render, except now it is the conversation that is trying to re-start on each render.
At the end of my attached forum post, I describe why using just join=true is not a practical solution for more complex scenarios involving nested flows.
> conversations re-started in pageflows
> -------------------------------------
>
> Key: JBSEAM-1292
> URL: http://jira.jboss.com/jira/browse/JBSEAM-1292
> Project: JBoss Seam
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2.1.GA
> Environment: Windows XP, JBoss 4.0.5, Eclipse & Exadel, IE 6.09, Seam-gen generated app, using MySQL 5 as the backend.
> Reporter: Andy Gibson
>
> See forum post :
> http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043286#4043286
> The problem is that when you use the <begin-conversation> tag in pages.xml with a pageflow. Any time the page is rendered within the pageflow, Seam attemps to re-perform the conversation requirements. (starting, joining or creating a new nested conversation).
> Note, this is only a problem when using a pageflow, without a pageflow, everything runs fine.
> If you use @Begin annotations on a method with a pageflow, then everything is fine.
> If you use s:link with conversation and pageflow attributes, then it runs fine.
> For the different attribute options, here are the results :
> <begin-conversation> results in an error (beginning conversation from long running conversation) as it tries to start a new conversation
> <begin-conversation join="true"> works ok because it just joins the conversation it started first time it hit the page
> <begin-conversation nested="true"> causes a new nested conversation to be created each time the page is rendered
> Somewhat similar to issue http://jira.jboss.org/jira/browse/JBSEAM-608 which was related to the pageflow re-starting on each render, except now it is the conversation that is trying to re-start on each render.
> At the end of my attached forum post, I describe why using just join=true is not a practical solution for more complex scenarios involving nested flows, and additionally, it makes nested flows impossible to use from pages.xml.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues
mailing list