[jboss-jira] [JBoss JIRA] Commented: (JBSEAM-372) s:link doesn't get parent conversation Id after exit of nested conversation
Christian Bauer (JIRA)
jira-events at jboss.com
Mon Oct 9 02:33:41 EDT 2006
[ http://jira.jboss.com/jira/browse/JBSEAM-372?page=comments#action_12344844 ]
Christian Bauer commented on JBSEAM-372:
----------------------------------------
Tested and works.
> s:link doesn't get parent conversation Id after exit of nested conversation
> ---------------------------------------------------------------------------
>
> Key: JBSEAM-372
> URL: http://jira.jboss.com/jira/browse/JBSEAM-372
> Project: JBoss Seam
> Issue Type: Bug
> Components: JSF
> Reporter: Christian Bauer
> Assigned To: Gavin King
> Fix For: 1.1
>
>
> Consider this sequence:
> - Conversation A -> s:link = startB(value, conversationId=A)
> - Nested B -> h:commandButton = Conversation.instance().endAndRedirect(conversationId=B);
> - Conversation A -> s:link = startB(value, conversationId=null)
> - crash
> Basically, it looks like s:link doesn't append a conversation id if the conversation is marked as being discarded after RENDER RESPONSE. This is the case in the RENDER_RESPONSE after the redirect out of Nested B, the conversation B will be discarded. So s:link renders without a conversation identifier. It should use the parent conversations identifier.
--
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 jboss-jira
mailing list