[
https://issues.apache.org/jira/browse/TRINIDAD-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeanne Waldman resolved TRINIDAD-757.
-------------------------------------
Resolution: Fixed
changed documentation, demo, and RequestContextImpl.java
Completed: At revision: 587555
on trunk
trinidad-build\src\main\resources\META-INF\maven-faces-plugin\components\trinidad\core\CoreMessages.xml
trinidad-build\src\main\resources\META-INF\maven-faces-plugin\components\trinidad\core\includes\CommonAttrs.xml
trinidad-examples\trinidaddemo\src\main\webapp\demos\pprDemos.jspx
trinidad-impl\src\main\java\org\apache\myfaces\trinidadinternal\context\RequestContextImpl.java
trinidad-impl\src\main\xrts\org\apache\myfaces\trinidadinternal\resource\LoggerBundle.xrts
> 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.
