[richfaces-issues] [JBoss JIRA] Updated: (RF-10426) a4j:ajax does not resolve absolute id in dataTable correctly

[Nick Belaevski (JIRA)]

     [ https://issues.jboss.org/browse/RF-10426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Belaevski updated RF-10426:
--------------------------------

         Assignee: Nick Belaevski
    Fix Version/s: 4.0.0.Milestone6


> a4j:ajax does not resolve absolute id in dataTable correctly
> ------------------------------------------------------------
>
>                 Key: RF-10426
>                 URL: https://issues.jboss.org/browse/RF-10426
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: core
>    Affects Versions: 4.0.0.Milestone5
>         Environment: RichFaces 4.0 trunk svn rev. 21417, mojarra 2.0.3
>            Reporter: Martin Kočí
>            Assignee: Nick Belaevski
>            Priority: Critical
>             Fix For: 4.0.0.Milestone6
>
>
> <h:form id="f">
>             <h:dataTable id="t">
>                     <h:column>
>                         <h:commandButton>
>                             <a4j:ajax render=":f:t:output"/>
>                         </h:commandButton>
>                     </h:column>
>                     <h:column >
>                         <h:outputText id="output"/>
>                     </h:column>
>             </h:dataTable>
> </h:form>
> asdresses component with absolute search expression with ":" at start. In such case CoreRendererUtils.findComponentsFor resolvers it as "f:t:output" but that not correct because button in a iterable component.
> If relative search expression "f:t:output" is used or f:ajax (with absolute or relativ expression) it works fine and expression is resolved for example as "f:t:3:output" for 4th row.
> I marked this as critical because it prevents component targeting in complex tree, for example target a element in outer table in render="" from command button in inner table.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira