[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3901) Conversation id is always propagated on redirects

[ https://jira.jboss.org/jira/browse/JBSEAM-3901?page=com.atlassian.jira.pl... ] Preben Ludviksen updated JBSEAM-3901: ------------------------------------- Description: According to the documentation, propagation of conversation id's on redirects is controlled by the redirect-filter: http://docs.jboss.com/seam/2.1.1.GA/reference/en-US/html/configuration.ht... However, the id propagates even if the filter is swithced off in components.xml: <web:redirect-filter disabled="true" installed="false"/> When redirecting using pages.xml: <page view-id="/login.xhtml"> <navigation> <rule if-outcome="success"> <redirect view-id="/servers.xhtml" /> </rule> </navigation> </page> According to the Seam user Peter Hilton in the referenced forum thread: "The <redirect/> results in a call to org.jboss.seam.faces.FacesManager.redirect(String viewId, Map<String, Object> parameters, boolean includeConversationId) This is called from the following code in org.jboss.seam.faces.Navigator which sets includeConversationId to true: FacesManager.instance().redirect(viewId, parameters, true);" The propagation should be possible to disable for use cases where you don't really rely on conversations, and don't want to clutter the URL. I have also posted a feature request to allow disabling of the propagation on a per-redirect basis: https://jira.jboss.org/jira/browse/JBSEAM-3902 was: According to the documentation, propagation of conversation id's on redirects is controlled by the redirect-filter: http://docs.jboss.com/seam/2.1.1.GA/reference/en-US/html/configuration.ht... However, the id propagates even if the filter is swithced off in components.xml: <web:redirect-filter disabled="true" installed="false"/> When redirecting using pages.xml: <page view-id="/login.xhtml"> <navigation> <rule if-outcome="success"> <redirect view-id="/servers.xhtml" /> </rule> </navigation> </page> According to the Seam user Peter Hilton in the referenced forum thread: "The <redirect/> results in a call to org.jboss.seam.faces.FacesManager.redirect(String viewId, Map<String, Object> parameters, boolean includeConversationId) This is called from the following code in org.jboss.seam.faces.Navigator which sets includeConversationId to true: FacesManager.instance().redirect(viewId, parameters, true);" The propagation should be possible to disable, for use cases where you don't really rely on conversations, and don't want to clutter the URL. I have also posted a feature request to allow disabling of the propagation on a per-redirect basis. -- 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