You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Rene O (Reopened) (JIRA)" <de...@myfaces.apache.org> on 2012/02/01 09:44:59 UTC

[jira] [Reopened] (MYFACES-3455) [myfaces-2.1.6-SNAPSHOT] Using f:ajax within h:commandButton to dynamic switch ui:include works not correct anymore

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

Rene O reopened MYFACES-3455:
-----------------------------


There is another problem:
If you use a component like a h:datatable with a <f:facet name="header"> and have there a link to dynamic switch the include 
and another child, then the switching doesn't work as expected. It only works, if you have only one child in f:facet.
Note, that this issue doesn't occur with myfaces-2.1.5

A new testcase is attached. To reproduce this issue open http://localhost:8080/jsftest2/newnavtest.jsf and click the button a few times to see what happens.
                
> [myfaces-2.1.6-SNAPSHOT] Using f:ajax within h:commandButton to dynamic switch ui:include works not correct anymore
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: MYFACES-3455
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3455
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions: 2.1.6-SNAPSHOT
>            Reporter: Rene O
>            Assignee: Leonardo Uribe
>            Priority: Blocker
>             Fix For: 2.0.12, 2.1.6
>
>         Attachments: jsftest.war, jsftest2.war
>
>
> If you click the ajaxified commandButton the ui:include switches. 
> After a few clicks, the switch doesn't work correct anymore. You must click twice to switch the include, which is a bug.
> A testcase to reproduce this issue is attached. Note, that this issue doesn't appear within myfaces 2.1.5
> http://localhost:8080/jsftest/navtest.jsf

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira