[
https://issues.jboss.org/browse/JBSEAM-5073?page=com.atlassian.jira.plugi...
]
Marek Schmidt commented on JBSEAM-5073:
---------------------------------------
a possible solution could perhaps be to check for
Contexts.getEventContext().isSet(REDIRECT_FROM_MANAGER) in the SeamViewHandler and modify
FacesManager to set the REDIRECT_FROM_MANAGER before calling
getViewHandler().getActionURL
(similar to RedirectFilter)
Programmatic redirect always add conversation id
------------------------------------------------
Key: JBSEAM-5073
URL:
https://issues.jboss.org/browse/JBSEAM-5073
Project: Seam 2
Issue Type: Bug
Components: JSF Integration
Affects Versions: 2.3.1.CR1
Environment: Seam 2.3.1-SNAPSHOT (2013-01-31)
Reporter: Marek Schmidt
Assignee: Marek Novotny
Priority: Critical
Fix For: 2.3.1.CR1
Seam redirect always propagates conversation, even when explicitly told not to. The
following code works in Seam 2.2, but now it redirects with the conversation id:
{code}
Redirect redirect = Redirect.instance();
redirect.setConversationPropagationEnabled(false);
redirect.setViewId("/output.xhtml");
redirect.execute();
{code}
This also propagates conversation:
{code}
FacesManager.instance().redirect("/output.xhtml", null, false, false);
{code}
The problem is likely in SeamViewHandler, which adds the cids. even with redirects.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira