myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bruno Aranda (JIRA)" <>
Subject [jira] Closed: (MYFACES-525) Myfaces does not handle correctly the from-view-id's with wildcards
Date Wed, 07 Sep 2005 07:13:30 GMT
     [ ]
Bruno Aranda closed MYFACES-525:

    Fix Version: 1.0.10m10
     Resolution: Fixed

The issue was not with the sort order, but with the parsing of from-view-id's with asterisks
In the case where a from-view-id ended with an asterisk, NavigationHandler didn't parse well
the prefix, and instead of removing only the asterisk it also removed the last letter.

> Myfaces does not handle correctly the from-view-id's with wildcards
> -------------------------------------------------------------------
>          Key: MYFACES-525
>          URL:
>      Project: MyFaces
>         Type: Bug
>   Components: JSR-127
>     Versions: 1.0.9m9
>     Reporter: Bruno Aranda
>     Assignee: Bruno Aranda
>      Fix For: 1.0.10m10

> From the spec (section 7.4.2, p5-10/11), when talking about the NavigationHandler:
> << Rule instances are
> considered in the following order:
> - An exact match of the view identifier against a <from-view-id> pattern that
> does not end with an asterisk ("*") character.
> - For <from-view-id> patterns that end with an asterisk, an exact match on
> characters preceding the asterisk against the prefix of the view id. If the
> patterns for multiple navigation rules match, pick the longest matching prefix
> first.
> - If there is a <navigation-rule> with a <from-view-id> pattern of only an
> asterisk, it matches any view identifier.>>
> In myfaces something happens with the from-view-id's with asterisk. Lets illustrate a
> 1. <from-view-id>test3</from-view-id>
> 2. <from-view-id>test*</from-view-id>
> 3. <from-view-id>*</from-view-id>
> I think that hibernate does not understand correctly the <from-view-id>'s with
asterisk. For instance, if I am in the a view with id 'tes' (sic), the from-view-id used is
the #2 when it should be the number #3.

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