Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 2.2 Sprint 8
    • Fix Version/s: None
    • Component/s: Navigation
    • Labels:
      None
    • Status Whiteboard:
      Hide

      size_small importance_medium

      Show
      size_small importance_medium

      Description

      Currently, implicit navigation seems to be enabled for all applications that
      are deployed on a container with Mojarra 2.0, even when they have a JSF 1.x
      configuration. Because some of the action methods in our 1.x applications can
      return an outcome that isn't defined in the navigation rules in faces-
      new view (one that possibly doesn't even exist) instead of doing nothing, like
      Mojarra 1.2 did.

      It would be great for maintaining compatibility with 1.x applications if
      implicit navigation is disabled when a 1.x configuration is found. Adding a
      context initialization parameter to explicitly disable implicit navigation
      could also be useful.
      Description
      Currently, implicit navigation seems to be enabled for all applications that are deployed on a container with Mojarra 2.0, even when they have a JSF 1.x configuration. Because some of the action methods in our 1.x applications can return an outcome that isn't defined in the navigation rules in faces- new view (one that possibly doesn't even exist) instead of doing nothing, like Mojarra 1.2 did. It would be great for maintaining compatibility with 1.x applications if implicit navigation is disabled when a 1.x configuration is found. Adding a context initialization parameter to explicitly disable implicit navigation could also be useful.

        Activity

        Hide
        rogerk added a comment -

        Additional comments from http://java.net/jira/secure/ViewProfile.jspa?name=omolenkamp

        Ok, Bugzilla / some javascript / my browser somehow strips a line starting at
        config dot xml. Last attempt:

        "Because some of the action methods in our 1.x applications can
        return an outcome that isn't defined in the navigation rules in faces dash
        config dot xml, Mojarra 2.0 will in such a case redirect to a new view (one
        that possibly doesn't even exist) instead of doing nothing, like
        Mojarra 1.2 did."

        Show
        rogerk added a comment - Additional comments from http://java.net/jira/secure/ViewProfile.jspa?name=omolenkamp Ok, Bugzilla / some javascript / my browser somehow strips a line starting at config dot xml. Last attempt: "Because some of the action methods in our 1.x applications can return an outcome that isn't defined in the navigation rules in faces dash config dot xml, Mojarra 2.0 will in such a case redirect to a new view (one that possibly doesn't even exist) instead of doing nothing, like Mojarra 1.2 did."
        Hide
        Ed Burns added a comment -

        Set priority to baseline ahead of JSF 2.3 triage. Priorities will be assigned accurately after this exercise.

        Show
        Ed Burns added a comment - Set priority to baseline ahead of JSF 2.3 triage. Priorities will be assigned accurately after this exercise.
        Hide
        Manfred Riem added a comment -

        Setting priority to Minor

        Show
        Manfred Riem added a comment - Setting priority to Minor

          People

          • Assignee:
            Unassigned
            Reporter:
            rogerk
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated: