myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacob Scherrer (JIRA)" <>
Subject [jira] Created: (MYFACES-1487) Wildcard navigation rule bug in NavigationHandlerImpl
Date Thu, 02 Nov 2006 22:14:16 GMT
Wildcard navigation rule bug in NavigationHandlerImpl

                 Key: MYFACES-1487
             Project: MyFaces Core
          Issue Type: Bug
    Affects Versions: 1.1.4
            Reporter: Jacob Scherrer

A navigation rule bug is present in NavigationHandlerImpl.calcMatchingNavigationCase(..)

The bug occurs in the following situation:

given the following navigation rules:



#{randomBean.newFoobar} returns "success"

If you are in the view /foo.jsp and an action link calling #{randomBean.newFoobar} is clicked,
the first navigation rule will be used. The reason is that the  the rule's actionRef and the
current actionRef are never compared, due to a logic error. This can be fixed by updating

            if (((cazeOutcome == outcome) || (cazeOutcome != null && cazeOutcome.equals(outcome)))
                ((cazeActionRef == actionRef) || (cazeActionRef != null && cazeActionRef.equals(actionRef))))
                return caze;

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message