myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leonardo Uribe (JIRA)" <>
Subject [jira] [Resolved] (MYFACES-3541) actionListener of composite component not working with dynamic includes
Date Thu, 10 May 2012 15:18:51 GMT


Leonardo Uribe resolved MYFACES-3541.

       Resolution: Fixed
    Fix Version/s: 2.1.8
         Assignee: Leonardo Uribe

I checked it carefully and the problem is all facelets components requires to be excluded
for the registration done with PreRemoveFromViewEvent. It seems I forget to include the component
that holds the composite component markup. Fortunately the fix is very simple and involves
just a few lines. Thanks a lot to Michael Heinen for the test, this is one of those that are
very difficult to understand or reproduce without a detailes test. It is a valuable contribution.
> actionListener of composite component not working with dynamic includes 
> ------------------------------------------------------------------------
>                 Key: MYFACES-3541
>                 URL:
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions: 2.1.7
>         Environment: tomcat 6.0.35
>            Reporter: Michael Heinen
>            Assignee: Leonardo Uribe
>             Fix For: 2.0.14, 2.1.8
>         Attachments: zIncludeCC.war
> I implemented a wizard with ui:includes.
> The current page of the wizard is included via a dynamic src attribute with an EL expression
pointing to the right page.
> The second page of this wizard contains a composite component with an actionListener
which is defined in the composite:interface.
> This actionListener is working well when this page of the wizard is visited the first
> The actionListener is not called anymore if user navigates back and forth in the wizard,
which results in other included components and a changed component tree.
> I'll attach a sample web archive and describe the steps in detail.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message