[jira] Resolved: (TRINIDAD-908) optimize invokeOnComponent in a namingContainer

["Gabrielle Crawford (JIRA)" <de...@myfaces.apache.org>]

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

Gabrielle Crawford resolved TRINIDAD-908.
-----------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.2.6-core

Completed: At revision: 613346  

This fix only applies in 1.2 branch as it deals with invokeOnComponent, which is new in JSF 1.2

> optimize invokeOnComponent in a namingContainer
> -----------------------------------------------
>
>                 Key: TRINIDAD-908
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-908
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>    Affects Versions: 1.2.5-core
>            Reporter: Gabrielle Crawford
>            Priority: Minor
>             Fix For: 1.2.6-core
>
>
> Avoid processing children based on id's in invokeOnComponent. 
> In UIXCollection it implements invokeOnComponent, and unless the client id passed in starts with the client id of the collection, it doesn't process the children. However not all our namingContainers are doing this.
> NamingContainers that don't avoid processing children based on id's in invokeOnComponent
>     * UIXComponentRef
>     * UIXDecorateCollection
>     * UIXMenu
>     * UIXSubform

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