[TRINIDAD-908] optimize invokeOnComponent in a namingContainer

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.2.5-core
• Fix Version/s: 1.2.6-core
• Assignee: Gabrielle Crawford
• Reporter: Gabrielle Crawford
• Created: 19/Jan/08 01:46
• Updated: 27/Jan/10 08:45
• Resolved: 19/Jan/08 02:55

Description

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