Uploaded image for project: 'Seam 2'
  1. Seam 2
  2. JBSEAM-1372

Previous conversation never ends when new one begins in the same request cycle

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Rejected
    • Affects Version/s: 1.2.1.GA
    • Fix Version/s: None
    • Component/s: Core
    • Labels:
      None
    • Environment:

      Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
      Ubuntu Linux 7.04
      Maven2+Jetty6

    • Affects:
      Documentation (Ref Guide, User Guide, etc.)
    • Workaround Description:
      Hide

      The easiest way to work around conversation propagation problems is just to use beforeRedirect=true. However, I find that I am having to do a lot of extra work to ensure that conversations are properly purged.

      Show
      The easiest way to work around conversation propagation problems is just to use beforeRedirect=true. However, I find that I am having to do a lot of extra work to ensure that conversations are properly purged.
    • Estimated Difficulty:
      Medium

      Description

      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

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                dan.j.allen Dan Allen
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 4 hours
                  4h
                  Remaining:
                  Remaining Estimate - 4 hours
                  4h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified