You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Matt Cooper (JIRA)" <de...@myfaces.apache.org> on 2008/01/30 23:09:37 UTC

[jira] Commented: (TRINIDAD-757) partialTriggers Contract Fails if direct parent component is not a NamingContainer

    [ https://issues.apache.org/jira/browse/TRINIDAD-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564193#action_12564193 ] 

Matt Cooper commented on TRINIDAD-757:
--------------------------------------

Note Andrew logged an RI bug against UIComponent's findComponent API:
https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=690

> partialTriggers Contract Fails if direct parent component is not a NamingContainer
> ----------------------------------------------------------------------------------
>
>                 Key: TRINIDAD-757
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-757
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Components
>    Affects Versions: 1.0.3-core, 1.2.2-core
>            Reporter: Matt Cooper
>            Assignee: Jeanne Waldman
>         Attachments: partialTriggers.jspx
>
>
> The definition of partialTriggers is:
> The IDs of the components that should trigger a partial update. This component will listen on the trigger components. If one of the trigger components receives an event that will cause it to update in some way, this component will request to be updated too. Identifiers are relative to the source component, and must account for NamingContainers. If your component is already inside of a naming container, you can use a single colon to start the search from the root, or multiple colons to move up through the NamingContainers - "::" will search from the parent naming container, ":::" will search from the grandparent naming container, etc.
> I am seeing that the multiple-colon use case will work as long as the direct parent component is a NamingContainer.  If the direct parent component is not a NamingContainer then one additional colon is incorrectly required to make it work.  I will upload a test page that demonstrates this shortly.

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