Bug 871933
| Summary: | RF-12304 : Two or more rich:extendedDataTable on page prevent selection on second extendedDataTable | ||
|---|---|---|---|
| Product: | [Retired] JBoss Enterprise WFK Platform 2 | Reporter: | ivassile |
| Component: | RichFaces | Assignee: | Brian Leathem <bleathem> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Pavol Pitonak <ppitonak> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.1.0 | CC: | kpiwko, mnovotny, myarboro |
| Target Milestone: | --- | ||
| Target Release: | 2.2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-02-13 08:54:45 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
ivassile
2012-10-31 18:28:44 UTC
Brian: Please add CCFR info for WFK 2.1 known issue. Brian, is this issue reproduced or you won't fix it at all? I don't get the answer from RF-12304 or from linked customer issue 00736257. The issue reported by the customer is not caused by the linked jira issue. GSS said they were going to work with the customer on reproducing the issue. I have not heard back from GSS. You can follow up with GSS as to the status of this issue. The client did not respond to my request [2] and I closed the case [1]. [1] 00736257 (https://c.na7.visual.force.com/apex/Case_View?id=500A000000Bdb0gIAB&sfdc.override=1) [2] Comment #17 on case [1]: >>> I'm reopening the case since the RichFaces developers have raised the following concerns: 1) You have an issue selecting rows in rich:extendedDataTable that is NOT caused by RF-12304 [1]. 2) Disabling PARTIAL_STATE_SAVING fixes your issue. 3) You are expecting that this will be fixed in the next release. Given that at this point we have no idea what is causing the problem, 3) seems unlikely. Without a reproduction of the error, we have no idea what to fix. [1] https://issues.jboss.org/browse/RF-12304 Regards, Ilia <<< Any update on this issue? Can we indeed close it? I don't have any updates from the customer. The case [1] is closed and you can close BZ issue. [1] https://c.na7.visual.force.com/apex/Case_View?id=500A000000Bdb0gIAB&sfdc.override=1 |