[
http://jira.jboss.com/jira/browse/JBSEAM-1243?page=all ]
Andrew reopened JBSEAM-1243:
----------------------------
I'm not sure how this can fix the issue. In 1.1.6, the code is:
if ( page.isConversationRequired() &&
!Manager.instance().isLongRunningConversation() )
{
Manager.instance().redirectToNoConversationView();
return result;
}
This looks like the same code in your comment above. This is the broken code. The problem
that I found was not in Pages.java, but rather in Manager.java.
The problem is that "Manager.instance().isLongRunningConversation() " returns
false if a nested conversation has been ended when it shouldn't. It should only return
false if the parent conversation has been ended.
Please correct me if I am in error.
Ending nested conversation causes issues with pages.xml and rendering
the same view again
-----------------------------------------------------------------------------------------
Key: JBSEAM-1243
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1243
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 1.1.6.GA
Reporter: Andrew
Assigned To: Gavin King
Fix For: 1.3.0.BETA1
Attachments: JBSEAM-1243.zip
See JBoss Forum Reference of this bug.
Will try to attach reproduce code in a bit.
--
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