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: 2.2.1.CR1
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