Description of problem: Seam adds conversation id even if the conversation is not long running. Version-Release number of selected component (if applicable): WFK 2.2.0.ER2 Seam 2.3.1.Final-redhat-1 Steps to Reproduce: 1. deploy booking example 2. go to http://127.0.0.1:8080/seam-booking/ 3. notice that "cid" is in the URL, e.g. http://127.0.0.1:8080/seam-booking/main.seam?cid=2 Actual results: There is a cid in the URL Expected results: no cid should be in the URL, as no conversation has begun yet. Additional Info: Note that the way how seam propagates conversation id has changed since Seam 2.2, so that now it uses the cid= in places where Seam2.2 would use the page context, so in some cases the "cid" parameter would be correctly present in a Seam2.3 application even if it was not present in the same Seam 2.2 application.
Actually, the reproducer is wrong, cid will always be added by a redirect. To reproduce this issue, do this instead: 1. create a seam-gen WAR application "myproject" 2. create a new action called "myAction" with "seam-gen new-action" 3. deploy with "ant" 4. go to http://127.0.0.1:8080/myproject/myAction.seam 5. click myAction 6. notice the "cid" is in the URL. Actual results: There is a cid in the URL Expected results: no cid should be in the URL, as no conversation has begun yet.
Marek S. provided patch, which is good enough to fix this - https://source.jboss.org/changelog/Seam?cs=15466
The fix introduced caused regressions in 2.2.0.CR1, see https://bugzilla.redhat.com/show_bug.cgi?id=928557, so this issue has to either be fixed differently, or the fix reverted.
The fix was reverted in https://source.jboss.org/changelog/Seam?cs=15471
Edited release note and inserted it into the 2.2.0 RN book. Docs stage URL: https://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Web_Framework_Kit/2.2/html-single/2.2.0_Release_Notes/index.html Build: JBoss_Web_Framework_Kit-2.2.0_Release_Notes-2.2-en-US-0-23
backported from upstream as https://source.jboss.org/changelog/Seam?cs=15491
Marek Novotny <mnovotny> updated the status of jira JBSEAM-5083 to Closed
Marek Novotny <mnovotny> made a comment on jira JBSEAM-5083 2.3.1.CR1 is now out, so closing all resolved issues
Verified on 2.3.0.ER1 release.
Updated doc text.