[
https://issues.jboss.org/browse/JBSEAM-5073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marek Novotny closed JBSEAM-5073.
---------------------------------
Resolution: Duplicate Issue
fixed by provided patch from JBSEAM-5066
> 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
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
