Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.2
    • Fix Version/s: None
    • Component/s: Flow
    • Labels:
      None

      Description

      Consider an app with this arrangement.

      src/main/webapp/WEB-INF/faces-config.xml
      src/main/webapp/flowA/flowA-flow.xml
      src/main/webapp/flowA/flowA.xhtml
      src/main/webapp/flowB/flowB-flow.xml
      src/main/webapp/flowB/flowB.xhtml
      src/main/webapp/flowC/flowC-flow.xml
      src/main/webapp/flowC/flowC.xhtml
      src/main/webapp/index.xhtml
      src/main/webapp/site-template.xhtml

      All .xhtml pages in this app are template clients of
      site-template.xhtml. The site-template.xhtml has a row of buttons along
      the top that allow immediate navigation to all of the flows. The intent
      is that whatever flow you're in, you want to abandon it and enter the
      new flow when the corresponding button is clicked. This is not a flow
      call, but rather should be treated as an atomic "abandon/enter".

      The current specification does not support this cleanly.

      1. i_spec_1253.patch
        42 kB
        Ed Burns

        Activity

          People

          • Assignee:
            Unassigned
            Reporter:
            Ed Burns
          • Votes:
            4 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated: