Uploaded image for project: 'MyFaces Trinidad'
  1. MyFaces Trinidad
  2. TRINIDAD-908

optimize invokeOnComponent in a namingContainer

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.2.5-core
    • Fix Version/s: 1.2.6-core
    • Component/s: None
    • Labels:
      None

      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

        Activity

        Hide
        gabrielle Gabrielle Crawford added a comment -

        Completed: At revision: 613346

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

        Show
        gabrielle Gabrielle Crawford added a comment - Completed: At revision: 613346 This fix only applies in 1.2 branch as it deals with invokeOnComponent, which is new in JSF 1.2

          People

          • Assignee:
            gabrielle Gabrielle Crawford
            Reporter:
            gabrielle Gabrielle Crawford
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development