You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org> on 2010/09/24 20:57:33 UTC

[jira] Resolved: (TOMAHAWK-1549) t:commandNavigation and t:commandNavigation2 has wrong DEFAULT_RENDERER_TYPE

     [ https://issues.apache.org/jira/browse/TOMAHAWK-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leonardo Uribe resolved TOMAHAWK-1549.
--------------------------------------

    Fix Version/s: 1.1.10-SNAPSHOT
       Resolution: Fixed

> t:commandNavigation and t:commandNavigation2 has wrong DEFAULT_RENDERER_TYPE
> ----------------------------------------------------------------------------
>
>                 Key: TOMAHAWK-1549
>                 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1549
>             Project: MyFaces Tomahawk
>          Issue Type: Bug
>          Components: Panel Navigation, Panel Navigation2
>    Affects Versions: 1.1.6
>            Reporter: Leonardo Uribe
>            Assignee: Leonardo Uribe
>             Fix For: 1.1.10-SNAPSHOT
>
>
> Finally I discover the reason why this is happening. 
> On tomahawk 1.1.6 we have the constant DEFAULT_RENDERER_TYPE set to javax.faces.Link, but the tag classes of this two components points to its renderers. Since with tomahawk 1.1.7 we now generate all component and tag classes, this detail was hidded and since javax.faces.Link was used, a renderer were found and finally the component worked.
> The solution is update this variable with the expected value, so when a t:commandNavigation or t:commandNavigation2 is rendered, the right component is used.

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