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

Support for controlled declarative destruction of part (or all) of the ConversationStack

    Details

    • Type: Feature Request
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.0.2.GA
    • Fix Version/s: None
    • Component/s: Core
    • Labels:
      None

      Description

      I think the solution proposed in JBSEAM-1943 is insufficient, it should allow for precise declarative control of how many levels of nested conversations should be destroyed (all of them or only some of them) using an EL expression, and not just the destruction of the entire ConversationStack.

      For example to end all nested conversation (but not root) (regardless of the nesting levels) something like:

      @End(levels="#

      {conversation.nestingLevel}") or <end-conversation levels="#{conversation.nestingLevel}

      "/>

      to end the root conversation (regardless of the nesting levels) something like

      @End(levels="#

      {conversation.nestingLevel+1}") or <end-conversation levels="#{conversation.nestingLevel+1}

      "/>

      to end two levels:
      @End(levels="#

      {2}" or <end-conversation levels="#{2}

      "/>

      Of course that means we would need to add the nestingLevel to conversation component (or create a new component to deal with this).

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  luxspes Francisco Jose Peredo Noguez
                • Votes:
                  6 Vote for this issue
                  Watchers:
                  7 Start watching this issue

                  Dates

                  • Created:
                    Updated: