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

Explicit conversation id is lost when using nested conversation

    Details

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

      Linux localhost 2.6.3-7mdk #1 Wed Mar 17 15:56:42 CET 2004 i686 unknown unknown GNU/Linux

      Description

      Each click on

      <s:link id="action" value="Act" action="#

      {somethingHome.beginAction}

      "/>

      @Begin(nested=true, id="action")
      public String beginAction() {
      }

      leads to creation of a new ConversationEntry, which means that explicit id is ignored.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                ebu Yevgen Bushuyev
              • Votes:
                1 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: