[
https://issues.jboss.org/browse/RF-12717?page=com.atlassian.jira.plugin.s...
]
Juraj Húska edited comment on RF-12717 at 1/16/13 8:57 AM:
-----------------------------------------------------------
Hey Brain,
*I can just confirm the reported behavior.*
* When deploying on {{EAP 6.0.1}} - exception is thrown.
* When application is deployed on {{EAP 6.0.0}}, no exception is thrown when working with
the table.
Changing {{<rich:dataTable>}} for {{<h:dataTable>}} and
{{<rich:column>}} for {{<h:column>}} make the code working as being said.
Please, let me know I can do more about this one.
was (Author: jhuska):
Hey Brain,
I can just confirm the reported behavior, when deploying on {{EAP 6.0.1}} - exception is
thrown.
When application is deployed on {{EAP 6.0.0}}, no exception is thrown when working with
the table.
Changing {{<rich:dataTable>}} for {{h:dataTable}} and {{rich:column}} for
{{h:column}} make the code working as being said.
Please, let me know I can do more about this one.
“Component ID <componentId> has already been found in the view”
exception when using rich:dataTable with JSF 2.1.13 on EAP 6.0.1.
---------------------------------------------------------------------------------------------------------------------------------
Key: RF-12717
URL:
https://issues.jboss.org/browse/RF-12717
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-tables
Affects Versions: 4.2.3.Final
Reporter: Ilia Vassilev
Assignee: Juraj Húska
Attachments: sample.rar
This is a problem with <richataTable>. The component id for each row is reused. If
you change the markup to use an ordinary <h:dataTable> and <h:column> then it
works correctly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira