[jira] Created: (TRINIDAD-1726) ProcessMenuModel & ProcessUtils will treat every train as if it were supposed to be a "Plus One" instead of a "Max Visited" case.

["Keith Carlton (JIRA)" <de...@myfaces.apache.org>]

ProcessMenuModel & ProcessUtils will treat every train as if it were supposed to be a "Plus One" instead of a "Max Visited" case.
---------------------------------------------------------------------------------------------------------------------------------

                 Key: TRINIDAD-1726
                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1726
             Project: MyFaces Trinidad
          Issue Type: Bug
          Components: Components
    Affects Versions: 1.2.13-core ,  1.2.12-core,  1.2.11-core
         Environment: CentOS 4 OS, Java 6, Eclipse 3.5.1, Tomcat 6.0.
            Reporter: Keith Carlton
            Priority: Minor


When attempting to create a "Max Visited" train component, you must specify a maxPathKey.  Whether this "maxPathKey" is set or not, the ProcessMenuModel (along with ProcessUtils) will treat every case as a "Plus One".  The issue is actually in org.apache.myfaces.trinidad.model.ProcessUtils in the isReadOnly method.  Below is the excerpt that causes the issue:

if (maxIndex == focusIndex)
        maxIndex = maxIndex + 1;

In testing, I extended the ProcessUtils & ProcessMenuModel and implemented my own version of isReadOnly with the above lines commented out, and I was able to get a "Max Visited" train to work.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.