[
https://issues.jboss.org/browse/RF-12717?page=com.atlassian.jira.plugin.s...
]
Juraj Húska edited comment on RF-12717 at 1/28/13 8:10 AM:
-----------------------------------------------------------
This is my story:
# I have removed all Spring dependencies from the provided sample and also other IMHO
non-important files, settings and *reproduced the issue on it as well*. This application
can be found [
here|https://github.com/jhuska/RF-12717].
# I have also tried to reproduce the issue on Metamer, on
[
this|https://github.com/richfaces/qa/tree/RF-12717] branch. I have used the same source
code, but *for the first time I was not successful.*
# I was looking for differences, and it seems that the only one important is: context
param {{javax.faces.PARTIAL_STATE_SAVING}} set to {{false}} in the application from the
first step.
# I *can reproduce the issue on metamer* as well by setting this context param to the
{{false}} in metamer's {{web.xml}}.
# The issue *disappears* by setting this context param to {{true}} on the *original
attached sample*.
Is the step 5 a valid workaround ?
The steps to reproduce the issue on my applications are the same as for the original
attached sample.
Just on metamer one needs to load:
http://localhost:8080/metamer/faces/components/richDataTable/rf-12717.xhtml
was (Author: jhuska):
This is my story:
# I have removed all Spring dependencies from the provided sample and also other IMHO
non-important files, settings and *reproduced the issue on it as well*. This application
can be found [
here|https://github.com/jhuska/RF-12717].
# I have also tried to reproduce the issue on Metamer, on
[
this|https://github.com/richfaces/qa/tree/RF-12717] branch. I have used the same source
code, but *for the first time I was not successful.*
# I was looking for differences, and it seems that the only one important is: context
param {{javax.faces.PARTIAL_STATE_SAVING}} set to {{false}} in the application from the
first step.
# I *can reproduce the issue on metamer* as well by setting this context param to the
{{false}} in metamer's {{web.xml}}.
# The issue *disappears* by setting this context param to {{true}} on the *original
attached sample*.
Is this a valid workaround ?
The steps to reproduce the issue on my applications are the same as for the original
attached sample.
Just on metamer one needs to load:
http://localhost:8080/metamer/faces/components/richDataTable/rf-12717.xhtml
“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: Brian Leathem
Fix For: 4.3.0.Final
Attachments: sample.rar
Original Estimate: 4 hours
Remaining Estimate: 4 hours
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