[seam-issues] [JBoss JIRA] Updated: (JBSEAM-4282) Seam-Wicket conversation propagation doesn't respect endBeforeRedirect

Norman Richards (JIRA) jira-events at lists.jboss.org
Sat Dec 19 16:04:30 EST 2009


     [ https://jira.jboss.org/jira/browse/JBSEAM-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Norman Richards updated JBSEAM-4282:
------------------------------------

    Fix Version/s: The future
                       (was: 2.2.1.CR1)


> Seam-Wicket conversation propagation doesn't respect endBeforeRedirect
> ----------------------------------------------------------------------
>
>                 Key: JBSEAM-4282
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-4282
>             Project: Seam
>          Issue Type: Bug
>          Components: Wicket
>    Affects Versions: 2.2.0.CR1
>            Reporter: Clint Popetz
>            Assignee: Clint Popetz
>             Fix For: The future
>
>
> SeamWebApplication and its inner classes use Manager.isLongRunningConversation to determine whether to propagate conversation ids across request targets, but if a user calls endBeforeRedirect and then redirects to a new page, that page will get the old conversation id.
> It should instead use the isReallyLongRunningConversation...a method whose very name suggests a design flaw :P 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the seam-issues mailing list