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

Andrew Robinson edited comment on TRINIDAD-1514 at 6/22/09 8:28 AM:
--------------------------------------------------------------------

That is not a bug. The include only happens once, and then the include will 
stamp out the component the include builds once per iteration. There is only 
one link component in your example, not several. You can also use 
f:setPropertyActionListener to set data based on the index or use the event 
passed into the actionListener to determine which loop is executing as the 
action event will be executed in context.

You can go to the demo here:
http://www.irian.at/trinidad-demo/faces/components/iterator.jspx

See _idJsp10:0:_idJsp12 vs _idJsp10:1:_idJsp12

To see that client ID's correctly get the index. If you have a use case 
otherwise, then submit a test case that shows when the client ID is not 
different per component stamp.

      was (Author: arobinson74):
    That is not a bug. The include only happens once, and then the include will 
stamp out the component the include builds once per iteration. There is only 
one link component in your example, not several. You can also use 
f:setPropertyActionListener to set data based on the index or use the event 
passed into the actionListener to determine which loop is executing as the 
action event will be executed in context.

In the future, please discuss issues on the users mailing list before 
submitting bugs.
  
> <tr:iterator> does not add index to id
> --------------------------------------
>
>                 Key: TRINIDAD-1514
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1514
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Components
>    Affects Versions:  1.2.12-core
>         Environment: IE7, Trinidad 1.2.11, JSF ri 1.2_12
>            Reporter: Dave
>
> <tr:iterator id="itr" value="#{bean.valueList}">
> <f:subview id="subPage">
>    <jsp:include page="subPage1.jsp" />
> </f:subview>  
> </tr:iterator>
> subPage1.jsp
> -------------------
> <tr:commandLink id="command" ...>
> All the comandLink IDs in the generated html are the same:  
> itr:subPage.command
> Suppose the  valueList has 10 elements,  10 commandLinks will be generated. 
> if any command link is clicked, all the 10 bound methods will be executed in 
> server side.  
> Indice need to be add to component id under <tr:iterator>. For the example 
> above.  IDs should be
> itr:0:subPage.command
> itr:1:subPage.command
> itr:2:subPage.command
> itr:3:subPage.command
> itr:4:subPage.command
> itr:5:subPage.command
> itr:6:subPage.command
> itr:7:subPage.command
> itr:8:subPage.command
> itr:9:subPage.command
> <tr:iterator> inside <tr:iterator> has the same problem.

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

Reply via email to