Bug 871933 - RF-12304 : Two or more rich:extendedDataTable on page prevent selection on second extendedDataTable
Summary: RF-12304 : Two or more rich:extendedDataTable on page prevent selection on se...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: JBoss Enterprise WFK Platform 2
Classification: Retired
Component: RichFaces
Version: 2.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 2.2.0
Assignee: Brian Leathem
QA Contact: Pavol Pitonak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-31 18:28 UTC by ivassile
Modified: 2018-11-29 19:33 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-02-13 08:54:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RF-12304 0 Major Resolved A javascript error is thrown when the number of frozen columns = total number of columns 2013-02-13 12:59:38 UTC

Description ivassile 2012-10-31 18:28:44 UTC
Description of problem:
If I place two or more extendedDataTables with selectionType="single" on one a page, it is only possible to make a selection on the first extendedDataTable. It is imposible to select a row on the second table. If I turn around the order of tables or delete the first one, it works fine for the other one.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
See https://issues.jboss.org/browse/RF-12304

Comment 2 mark yarborough 2012-11-09 14:51:09 UTC
Brian: Please add CCFR info for WFK 2.1 known issue.

Comment 4 Marek Novotny 2013-01-10 12:11:53 UTC
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.

Comment 5 Brian Leathem 2013-01-10 17:41:54 UTC
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.

Comment 6 ivassile 2013-01-10 18:00:10 UTC
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
<<<

Comment 7 Brian Leathem 2013-02-12 21:04:30 UTC
Any update on this issue?  Can we indeed close it?

Comment 8 ivassile 2013-02-12 21:21:07 UTC
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

Comment 9 JBoss JIRA Server 2013-02-12 22:15:00 UTC
Brian Leathem <bleathem> updated the status of jira RF-12304 to Resolved


Note You need to log in before you can comment on or make changes to this bug.