glassfish
  1. glassfish
  2. GLASSFISH-19941

Flow is not created when we define our flow using java code and no other flow(using xml) is defined in the app

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 4.0_b80_EE7MS6
    • Fix Version/s: 4.0_b82_EE7MS7
    • Component/s: jsf
    • Labels:
      None
    • Environment:

      Glassfish 4.0 b80, Mojarra 2.2.0-m11

      Description

      Scenario:

      I am trying to create a Flows sample application. Here I am trying to create a flow inside a folder at the root of web application and the flow is defined programatically using the @FlowDefinition annotation .

      This application doesn't have any other flows defined. When I deploy the application , JSF runtime doesn't recognize that the application has faces flow defined, and the app doesn't work

      But this works when the application has another flow defined with the views declared in a directory inside webapp root directory and flow is defined using flow.xml file in the same folder as views.

        Issue Links

          Activity

          Hide
          Ed Burns added a comment -

          M jsf-ri/src/main/java/com/sun/faces/application/ApplicationAssociate.java

          • Instead of considering XML as the only means for determining the
            existence of flows in an app, use XML or the builder API.

          M jsf-ri/src/main/java/com/sun/faces/application/NavigationHandlerImpl.java

          • Handle the case of flow popping when a another node calls a
            <flow-return>.

          M jsf-ri/src/main/java/com/sun/faces/flow/FlowImpl.java

          • Facilitate the above mentioned change in NavigationHandler by
            providing a constant that can be checked to accurately trap the case.
            Sending jsf-ri/src/main/java/com/sun/faces/application/ApplicationAssociate.java
            Sending jsf-ri/src/main/java/com/sun/faces/application/NavigationHandlerImpl.java
            Sending jsf-ri/src/main/java/com/sun/faces/flow/FlowImpl.java
            Transmitting file data ...
            Committed revision 11774.
          Show
          Ed Burns added a comment - M jsf-ri/src/main/java/com/sun/faces/application/ApplicationAssociate.java Instead of considering XML as the only means for determining the existence of flows in an app, use XML or the builder API. M jsf-ri/src/main/java/com/sun/faces/application/NavigationHandlerImpl.java Handle the case of flow popping when a another node calls a <flow-return>. M jsf-ri/src/main/java/com/sun/faces/flow/FlowImpl.java Facilitate the above mentioned change in NavigationHandler by providing a constant that can be checked to accurately trap the case. Sending jsf-ri/src/main/java/com/sun/faces/application/ApplicationAssociate.java Sending jsf-ri/src/main/java/com/sun/faces/application/NavigationHandlerImpl.java Sending jsf-ri/src/main/java/com/sun/faces/flow/FlowImpl.java Transmitting file data ... Committed revision 11774.
          Hide
          Ed Burns added a comment -

          Committed to MOJARRA_2_0_0_GLASSFISH_4_0 branch.

          merge from trunk

          SECTION: Modified Files
          ----------------------------
          M jsf-ri/src/main/java/com/sun/faces/application/ApplicationAssociate.java

          • Instead of considering XML as the only means for determining the
            existence of flows in an app, use XML or the builder API.

          M jsf-ri/src/main/java/com/sun/faces/application/NavigationHandlerImpl.java

          • Handle the case of flow popping when a another node calls a
            <flow-return>.

          M jsf-ri/src/main/java/com/sun/faces/flow/FlowImpl.java

          • Facilitate the above mentioned change in NavigationHandler by
            providing a constant that can be checked to accurately trap the case.
            Sending jsf-ri/src/main/java/com/sun/faces/application/ApplicationAssociate.java
            Sending jsf-ri/src/main/java/com/sun/faces/application/NavigationHandlerImpl.java
            Sending jsf-ri/src/main/java/com/sun/faces/flow/FlowImpl.java
            Transmitting file data ...
            Committed revision 11775.
          Show
          Ed Burns added a comment - Committed to MOJARRA_2_0_0_GLASSFISH_4_0 branch. merge from trunk SECTION: Modified Files ---------------------------- M jsf-ri/src/main/java/com/sun/faces/application/ApplicationAssociate.java Instead of considering XML as the only means for determining the existence of flows in an app, use XML or the builder API. M jsf-ri/src/main/java/com/sun/faces/application/NavigationHandlerImpl.java Handle the case of flow popping when a another node calls a <flow-return>. M jsf-ri/src/main/java/com/sun/faces/flow/FlowImpl.java Facilitate the above mentioned change in NavigationHandler by providing a constant that can be checked to accurately trap the case. Sending jsf-ri/src/main/java/com/sun/faces/application/ApplicationAssociate.java Sending jsf-ri/src/main/java/com/sun/faces/application/NavigationHandlerImpl.java Sending jsf-ri/src/main/java/com/sun/faces/flow/FlowImpl.java Transmitting file data ... Committed revision 11775.

            People

            • Assignee:
              Ed Burns
              Reporter:
              Sreekanth
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: