[
http://jira.jboss.com/jira/browse/JBSEAM-1372?page=all ]
Gavin King closed JBSEAM-1372.
------------------------------
Resolution: Rejected
Your expectation is incorrect. Conversations are always bigger than requests. This is not
a bug.
Previous conversation never ends when new one begins in the same
request cycle
------------------------------------------------------------------------------
Key: JBSEAM-1372
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1372
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.2.1.GA
Environment: Java(TM) 2 Runtime Environment, Standard Edition (build
1.5.0_06-b05)
Ubuntu Linux 7.04
Maven2+Jetty6
Reporter: Dan Allen
Original Estimate: 4 hours
Remaining Estimate: 4 hours
If you navigate using the s:link tag with propagation="end" OR invoke an action
that is marked with the @End annotation (without beforeRedirect) AND THEN render a page
which starts a new conversation (either via a factory or a page action), the previous
conversation gets recycled. I would expect that conversation id would increment by 1 and
the old conversation would be garbage collected. However, this is not the case, and the
two conversations merge.
Scenario:
Create a page that begins a conversation
In that page, include a link that ends the conversation and renders the next page:
<s:link action="#{myAction.endAndGotoNext}" /> where @End
MyAction#endAndGotoNext()
In the next page that is rendered begin a conversation (either via a factory or a page
action)
Now use /debug.seam page to see that the conversation id is never killed from the first
page
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira