[JBoss JIRA] Created: (RF-11060) onselectionchange working incorrect with two extendedDataTable on same page
9:58 p.m.
onselectionchange working incorrect with two extendedDataTable on same page
---------------------------------------------------------------------------
Key: RF-11060
URL: https://issues.jboss.org/browse/RF-11060
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.0.0.Final
Environment: GlassFish 3.0.1, Firefox
Reporter: Tom Giberius
Priority: Critical
If you put two extendedDataTable A en B on the same page then the following goes wrong:
If you selected record one of Table A en then select record one from table B then the
onselectionchange trigger does not fire. The same counts for record two, three, etc.
This prevents me for building a Master-Detail data entry screen where both the master and
the detail are multirecord. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in details, then go back to record 3 of master and then the
onselectionchange trigger does not fire. The master tables "thinks" that record
three is the selected record while actually it should be record one which was the selected
record in the master table.
The correct behaviour should be that each table should "rember" it selected
record. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in detail, then go back to record 3 of master and the
onselectionchange of the master should fire so that details of master record 3 can be
shown. If you would have go back to record one of the master then not firing the
onselectionchange would be correct.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:27 p.m.
New subject: [JBoss JIRA] Updated: (RF-11060) onselectionchange working incorrect with two extendedDataTable on same page
[
https://issues.jboss.org/browse/RF-11060?page=com.atlassian.jira.plugin.s...
]
Jay Balunas updated RF-11060:
-----------------------------
Assignee: Pavol Pitonak
Forum Reference: http://community.jboss.org/thread/167554 (was:
http://community.jboss.org/thread/167554)
Pavol please verify, and if accurate assign to 4.1.M1
onselectionchange working incorrect with two extendedDataTable on
same page
---------------------------------------------------------------------------
Key: RF-11060
URL: https://issues.jboss.org/browse/RF-11060
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.0.0.Final
Environment: GlassFish 3.0.1, Firefox
Reporter: Tom Giberius
Assignee: Pavol Pitonak
Priority: Critical
If you put two extendedDataTable A en B on the same page then the following goes wrong:
If you selected record one of Table A en then select record one from table B then the
onselectionchange trigger does not fire. The same counts for record two, three, etc.
This prevents me for building a Master-Detail data entry screen where both the master and
the detail are multirecord. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in details, then go back to record 3 of master and then the
onselectionchange trigger does not fire. The master tables "thinks" that record
three is the selected record while actually it should be record one which was the selected
record in the master table.
The correct behaviour should be that each table should "rember" it selected
record. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in detail, then go back to record 3 of master and the
onselectionchange of the master should fire so that details of master record 3 can be
shown. If you would have go back to record one of the master then not firing the
onselectionchange would be correct.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:42 p.m.
New subject: [JBoss JIRA] Assigned: (RF-11060) onselectionchange working incorrect with two extendedDataTable on same page
[
https://issues.jboss.org/browse/RF-11060?page=com.atlassian.jira.plugin.s...
]
Pavol Pitonak reassigned RF-11060:
----------------------------------
Assignee: Jay Balunas (was: Pavol Pitonak)
I can reproduce with following environment:
* RichFaces 4.1.0-SNAPSHOT
* Metamer 4.1.0-SNAPSHOT r.22517
* Mojarra 2.1.0-FCS
* GlassFish Server Open Source Edition 3.1
* Java(TM) SE Runtime Environment 1.6.0_24-b07 @ Linux
* Firefox 3.6.17 @ Linux x86_64
I noticed that bug happens only when the same line is selected in both tables (e.g. select
fifth line in both).
onselectionchange working incorrect with two extendedDataTable on
same page
---------------------------------------------------------------------------
Key: RF-11060
URL: https://issues.jboss.org/browse/RF-11060
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.0.0.Final
Environment: GlassFish 3.0.1, Firefox
Reporter: Tom Giberius
Assignee: Jay Balunas
Priority: Critical
Fix For: 4.1.0.Milestone1
If you put two extendedDataTable A en B on the same page then the following goes wrong:
If you selected record one of Table A en then select record one from table B then the
onselectionchange trigger does not fire. The same counts for record two, three, etc.
This prevents me for building a Master-Detail data entry screen where both the master and
the detail are multirecord. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in details, then go back to record 3 of master and then the
onselectionchange trigger does not fire. The master tables "thinks" that record
three is the selected record while actually it should be record one which was the selected
record in the master table.
The correct behaviour should be that each table should "rember" it selected
record. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in detail, then go back to record 3 of master and the
onselectionchange of the master should fire so that details of master record 3 can be
shown. If you would have go back to record one of the master then not firing the
onselectionchange would be correct.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:42 p.m.
New subject: [JBoss JIRA] Updated: (RF-11060) onselectionchange working incorrect with two extendedDataTable on same page
[
https://issues.jboss.org/browse/RF-11060?page=com.atlassian.jira.plugin.s...
]
Pavol Pitonak updated RF-11060:
-------------------------------
Fix Version/s: 4.1.0.Milestone1
Forum Reference: http://community.jboss.org/thread/167554 (was:
http://community.jboss.org/thread/167554)
onselectionchange working incorrect with two extendedDataTable on
same page
---------------------------------------------------------------------------
Key: RF-11060
URL: https://issues.jboss.org/browse/RF-11060
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.0.0.Final
Environment: GlassFish 3.0.1, Firefox
Reporter: Tom Giberius
Assignee: Jay Balunas
Priority: Critical
Fix For: 4.1.0.Milestone1
If you put two extendedDataTable A en B on the same page then the following goes wrong:
If you selected record one of Table A en then select record one from table B then the
onselectionchange trigger does not fire. The same counts for record two, three, etc.
This prevents me for building a Master-Detail data entry screen where both the master and
the detail are multirecord. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in details, then go back to record 3 of master and then the
onselectionchange trigger does not fire. The master tables "thinks" that record
three is the selected record while actually it should be record one which was the selected
record in the master table.
The correct behaviour should be that each table should "rember" it selected
record. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in detail, then go back to record 3 of master and the
onselectionchange of the master should fire so that details of master record 3 can be
shown. If you would have go back to record one of the master then not firing the
onselectionchange would be correct.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:51 p.m.
New subject: [JBoss JIRA] Commented: (RF-11060) onselectionchange working incorrect with two extendedDataTable on same page
[
https://issues.jboss.org/browse/RF-11060?page=com.atlassian.jira.plugin.s...
]
Tom Giberius commented on RF-11060:
-----------------------------------
The bug is indeed when the same record in a table is selected.
Table A - record 1 => onselectionchange fires, that's ok.
Table B - record 3 => onselectionchange fires, that's ok.
Table A - record 3 => now onselectionchange does not fire, that's the bug.
onselectionchange working incorrect with two extendedDataTable on
same page
---------------------------------------------------------------------------
Key: RF-11060
URL: https://issues.jboss.org/browse/RF-11060
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.0.0.Final
Environment: GlassFish 3.0.1, Firefox
Reporter: Tom Giberius
Assignee: Jay Balunas
Priority: Critical
Fix For: 4.1.0.Milestone1
If you put two extendedDataTable A en B on the same page then the following goes wrong:
If you selected record one of Table A en then select record one from table B then the
onselectionchange trigger does not fire. The same counts for record two, three, etc.
This prevents me for building a Master-Detail data entry screen where both the master and
the detail are multirecord. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in details, then go back to record 3 of master and then the
onselectionchange trigger does not fire. The master tables "thinks" that record
three is the selected record while actually it should be record one which was the selected
record in the master table.
The correct behaviour should be that each table should "rember" it selected
record. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in detail, then go back to record 3 of master and the
onselectionchange of the master should fire so that details of master record 3 can be
shown. If you would have go back to record one of the master then not firing the
onselectionchange would be correct.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:01 a.m.
New subject: [JBoss JIRA] Updated: (RF-11060) onselectionchange working incorrect with two extendedDataTable on same page
[
https://issues.jboss.org/browse/RF-11060?page=com.atlassian.jira.plugin.s...
]
Jay Balunas updated RF-11060:
-----------------------------
Fix Version/s: 4.1.0.Final
(was: 4.1.0.Milestone1)
Forum Reference: http://community.jboss.org/thread/167554 (was:
http://community.jboss.org/thread/167554)
onselectionchange working incorrect with two extendedDataTable on
same page
---------------------------------------------------------------------------
Key: RF-11060
URL: https://issues.jboss.org/browse/RF-11060
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.0.0.Final
Environment: GlassFish 3.0.1, Firefox
Reporter: Tom Giberius
Assignee: Jay Balunas
Priority: Critical
Fix For: 4.1.0.Final
If you put two extendedDataTable A en B on the same page then the following goes wrong:
If you selected record one of Table A en then select record one from table B then the
onselectionchange trigger does not fire. The same counts for record two, three, etc.
This prevents me for building a Master-Detail data entry screen where both the master and
the detail are multirecord. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in details, then go back to record 3 of master and then the
onselectionchange trigger does not fire. The master tables "thinks" that record
three is the selected record while actually it should be record one which was the selected
record in the master table.
The correct behaviour should be that each table should "rember" it selected
record. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in detail, then go back to record 3 of master and the
onselectionchange of the master should fire so that details of master record 3 can be
shown. If you would have go back to record one of the master then not firing the
onselectionchange would be correct.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:27 p.m.
New subject: [JBoss JIRA] Assigned: (RF-11060) onselectionchange working incorrect with two extendedDataTable on same page
[
https://issues.jboss.org/browse/RF-11060?page=com.atlassian.jira.plugin.s...
]
Jay Balunas reassigned RF-11060:
--------------------------------
Assignee: (was: Jay Balunas)
onselectionchange working incorrect with two extendedDataTable on
same page
---------------------------------------------------------------------------
Key: RF-11060
URL: https://issues.jboss.org/browse/RF-11060
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.0.0.Final
Environment: GlassFish 3.0.1, Firefox
Reporter: Tom Giberius
Priority: Critical
Fix For: 4.1.0.Final
If you put two extendedDataTable A en B on the same page then the following goes wrong:
If you selected record one of Table A en then select record one from table B then the
onselectionchange trigger does not fire. The same counts for record two, three, etc.
This prevents me for building a Master-Detail data entry screen where both the master and
the detail are multirecord. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in details, then go back to record 3 of master and then the
onselectionchange trigger does not fire. The master tables "thinks" that record
three is the selected record while actually it should be record one which was the selected
record in the master table.
The correct behaviour should be that each table should "rember" it selected
record. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in detail, then go back to record 3 of master and the
onselectionchange of the master should fire so that details of master record 3 can be
shown. If you would have go back to record one of the master then not firing the
onselectionchange would be correct.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:20 p.m.
New subject: [JBoss JIRA] Updated: (RF-11060) onselectionchange working incorrect with two extendedDataTable on same page
[
https://issues.jboss.org/browse/RF-11060?page=com.atlassian.jira.plugin.s...
]
Jay Balunas updated RF-11060:
-----------------------------
Component/s: component-selects
component-tables
Forum Reference: http://community.jboss.org/thread/167554 (was:
http://community.jboss.org/thread/167554)
onselectionchange working incorrect with two extendedDataTable on
same page
---------------------------------------------------------------------------
Key: RF-11060
URL: https://issues.jboss.org/browse/RF-11060
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-selects, component-tables
Affects Versions: 4.0.0.Final
Environment: GlassFish 3.0.1, Firefox
Reporter: Tom Giberius
Priority: Critical
Fix For: 4.1.0.Final
If you put two extendedDataTable A en B on the same page then the following goes wrong:
If you selected record one of Table A en then select record one from table B then the
onselectionchange trigger does not fire. The same counts for record two, three, etc.
This prevents me for building a Master-Detail data entry screen where both the master and
the detail are multirecord. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in details, then go back to record 3 of master and then the
onselectionchange trigger does not fire. The master tables "thinks" that record
three is the selected record while actually it should be record one which was the selected
record in the master table.
The correct behaviour should be that each table should "rember" it selected
record. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in detail, then go back to record 3 of master and the
onselectionchange of the master should fire so that details of master record 3 can be
shown. If you would have go back to record one of the master then not firing the
onselectionchange would be correct.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:22 p.m.
New subject: [JBoss JIRA] Updated: (RF-11060) onselectionchange working incorrect with two extendedDataTable on same page
[
https://issues.jboss.org/browse/RF-11060?page=com.atlassian.jira.plugin.s...
]
Jay Balunas updated RF-11060:
-----------------------------
Fix Version/s: 4.1.0.Milestone2
(was: 4.1.0.Final)
Forum Reference: http://community.jboss.org/thread/167554 (was:
http://community.jboss.org/thread/167554)
onselectionchange working incorrect with two extendedDataTable on
same page
---------------------------------------------------------------------------
Key: RF-11060
URL: https://issues.jboss.org/browse/RF-11060
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-selects, component-tables
Affects Versions: 4.0.0.Final
Environment: GlassFish 3.0.1, Firefox
Reporter: Tom Giberius
Priority: Critical
Fix For: 4.1.0.Milestone2
If you put two extendedDataTable A en B on the same page then the following goes wrong:
If you selected record one of Table A en then select record one from table B then the
onselectionchange trigger does not fire. The same counts for record two, three, etc.
This prevents me for building a Master-Detail data entry screen where both the master and
the detail are multirecord. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in details, then go back to record 3 of master and then the
onselectionchange trigger does not fire. The master tables "thinks" that record
three is the selected record while actually it should be record one which was the selected
record in the master table.
The correct behaviour should be that each table should "rember" it selected
record. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in detail, then go back to record 3 of master and the
onselectionchange of the master should fire so that details of master record 3 can be
shown. If you would have go back to record one of the master then not firing the
onselectionchange would be correct.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:13 a.m.
New subject: [JBoss JIRA] Updated: (RF-11060) onselectionchange working incorrect with two extendedDataTable on same page
[
https://issues.jboss.org/browse/RF-11060?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-11060:
-------------------------------
Steps to Reproduce:
Try this code to reproduce (it is different from my real code but it does show the
error):
{code}
<h:form id="tom" prependId="false" >
Lijst A <br/>
<rich:extendedDataTable
value="#{test.a}"
var ="lijstA"
onselectionchange="alert('a')"
<rich:column>
<h:inputText value="#{lijstA.naam}" />
</rich:column>
</rich:extendedDataTable>
</h:form>
<h:form id="gib" prependId="false" >
Lijst B <br/>
<rich:extendedDataTable
value="#{test.b}"
var ="lijstB"
onselectionchange="alert('b')"
<rich:column>
<h:inputText value="#{lijstB.naam}" />
</rich:column>
</rich:extendedDataTable>
</h:form>
{code}
{code}
@Named(value="test")
@SessionScoped
public class Test implements Serializable{
private List<Hond> A = new ArrayList<Hond>();
private List<Hond> B = new ArrayList<Hond>();
/** Creates a new instance of Test */
public Test() {
}
@PostConstruct
public void init() {
A.add(new Hond("A"));
A.add(new Hond("B"));
A.add(new Hond("C"));
B.add(new Hond("D"));
B.add(new Hond("E"));
B.add(new Hond("F"));
}
public List<Hond> getA() {
return A;
}
public void setA(List<Hond> A) {
this.A = A;
}
public List<Hond> getB() {
return B;
}
public void setB(List<Hond> B) {
this.B = B;
}
public class Hond {
private String naam;
public Hond() {
}
public Hond(String naam) {
this.naam = naam;
}
public String getNaam() {
return naam;
}
public void setNaam(String naam) {
this.naam = naam;
}
}
{code}
was:
Try this code to reproduce (it is different from my real code but it does show the
error):
<h:form id="tom" prependId="false" >
Lijst A <br/>
<rich:extendedDataTable
value="#{test.a}"
var ="lijstA"
onselectionchange="alert('a')"
<rich:column>
<h:inputText value="#{lijstA.naam}" />
</rich:column>
</rich:extendedDataTable>
</h:form>
<h:form id="gib" prependId="false" >
Lijst B <br/>
<rich:extendedDataTable
value="#{test.b}"
var ="lijstB"
onselectionchange="alert('b')"
<rich:column>
<h:inputText value="#{lijstB.naam}" />
</rich:column>
</rich:extendedDataTable>
</h:form>
@Named(value="test")
@SessionScoped
public class Test implements Serializable{
private List<Hond> A = new ArrayList<Hond>();
private List<Hond> B = new ArrayList<Hond>();
/** Creates a new instance of Test */
public Test() {
}
@PostConstruct
public void init() {
A.add(new Hond("A"));
A.add(new Hond("B"));
A.add(new Hond("C"));
B.add(new Hond("D"));
B.add(new Hond("E"));
B.add(new Hond("F"));
}
public List<Hond> getA() {
return A;
}
public void setA(List<Hond> A) {
this.A = A;
}
public List<Hond> getB() {
return B;
}
public void setB(List<Hond> B) {
this.B = B;
}
public class Hond {
private String naam;
public Hond() {
}
public Hond(String naam) {
this.naam = naam;
}
public String getNaam() {
return naam;
}
public void setNaam(String naam) {
this.naam = naam;
}
}
Forum Reference: http://community.jboss.org/thread/167554 (was:
http://community.jboss.org/thread/167554)
onselectionchange working incorrect with two extendedDataTable on
same page
---------------------------------------------------------------------------
Key: RF-11060
URL: https://issues.jboss.org/browse/RF-11060
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-selects, component-tables
Affects Versions: 4.0.0.Final
Environment: GlassFish 3.0.1, Firefox
Reporter: Tom Giberius
Priority: Critical
Fix For: 4.1.0.Milestone2
If you put two extendedDataTable A en B on the same page then the following goes wrong:
If you selected record one of Table A en then select record one from table B then the
onselectionchange trigger does not fire. The same counts for record two, three, etc.
This prevents me for building a Master-Detail data entry screen where both the master and
the detail are multirecord. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in details, then go back to record 3 of master and then the
onselectionchange trigger does not fire. The master tables "thinks" that record
three is the selected record while actually it should be record one which was the selected
record in the master table.
The correct behaviour should be that each table should "rember" it selected
record. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in detail, then go back to record 3 of master and the
onselectionchange of the master should fire so that details of master record 3 can be
shown. If you would have go back to record one of the master then not firing the
onselectionchange would be correct.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:30 a.m.
New subject: [JBoss JIRA] Updated: (RF-11060) onselectionchange working incorrect with two extendedDataTable on same page
[
https://issues.jboss.org/browse/RF-11060?page=com.atlassian.jira.plugin.s...
]
Jay Balunas updated RF-11060:
-----------------------------
Fix Version/s: 4.1.0.Tracking
(was: 4.1.0.Milestone2)
Forum Reference: http://community.jboss.org/thread/167554 (was:
http://community.jboss.org/thread/167554)
onselectionchange working incorrect with two extendedDataTable on
same page
---------------------------------------------------------------------------
Key: RF-11060
URL: https://issues.jboss.org/browse/RF-11060
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-selects, component-tables
Affects Versions: 4.0.0.Final
Environment: GlassFish 3.0.1, Firefox
Reporter: Tom Giberius
Priority: Critical
Fix For: 4.1.0.Tracking
If you put two extendedDataTable A en B on the same page then the following goes wrong:
If you selected record one of Table A en then select record one from table B then the
onselectionchange trigger does not fire. The same counts for record two, three, etc.
This prevents me for building a Master-Detail data entry screen where both the master and
the detail are multirecord. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in details, then go back to record 3 of master and then the
onselectionchange trigger does not fire. The master tables "thinks" that record
three is the selected record while actually it should be record one which was the selected
record in the master table.
The correct behaviour should be that each table should "rember" it selected
record. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in detail, then go back to record 3 of master and the
onselectionchange of the master should fire so that details of master record 3 can be
shown. If you would have go back to record one of the master then not firing the
onselectionchange would be correct.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:33 a.m.
New subject: [JBoss JIRA] Assigned: (RF-11060) onselectionchange working incorrect with two extendedDataTable on same page
[
https://issues.jboss.org/browse/RF-11060?page=com.atlassian.jira.plugin.s...
]
Ilya Shaikovsky reassigned RF-11060:
------------------------------------
Assignee: Lukáš Fryč
Lukas, as its critical I wanted to help to review and founf out that that pull request
https://github.com/richfaces/components/pull/12
which is already integrated - resolves the issue.
So you guys could re-check and resolve.
onselectionchange working incorrect with two extendedDataTable on
same page
---------------------------------------------------------------------------
Key: RF-11060
URL: https://issues.jboss.org/browse/RF-11060
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-selects, component-tables
Affects Versions: 4.0.0.Final
Environment: GlassFish 3.0.1, Firefox
Reporter: Tom Giberius
Assignee: Lukáš Fryč
Priority: Critical
Fix For: 4.1.0.Tracking
If you put two extendedDataTable A en B on the same page then the following goes wrong:
If you selected record one of Table A en then select record one from table B then the
onselectionchange trigger does not fire. The same counts for record two, three, etc.
This prevents me for building a Master-Detail data entry screen where both the master and
the detail are multirecord. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in details, then go back to record 3 of master and then the
onselectionchange trigger does not fire. The master tables "thinks" that record
three is the selected record while actually it should be record one which was the selected
record in the master table.
The correct behaviour should be that each table should "rember" it selected
record. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in detail, then go back to record 3 of master and the
onselectionchange of the master should fire so that details of master record 3 can be
shown. If you would have go back to record one of the master then not firing the
onselectionchange would be correct.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:18 a.m.
New subject: [JBoss JIRA] Commented: (RF-11060) onselectionchange working incorrect with two extendedDataTable on same page
[
https://issues.jboss.org/browse/RF-11060?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč commented on RF-11060:
---------------------------------
Thanks for letting us know, Ilya, I will try locally and resolve.
onselectionchange working incorrect with two extendedDataTable on
same page
---------------------------------------------------------------------------
Key: RF-11060
URL: https://issues.jboss.org/browse/RF-11060
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-selects, component-tables
Affects Versions: 4.0.0.Final
Environment: GlassFish 3.0.1, Firefox
Reporter: Tom Giberius
Assignee: Lukáš Fryč
Priority: Critical
Fix For: 4.1.0.Milestone3
If you put two extendedDataTable A en B on the same page then the following goes wrong:
If you selected record one of Table A en then select record one from table B then the
onselectionchange trigger does not fire. The same counts for record two, three, etc.
This prevents me for building a Master-Detail data entry screen where both the master and
the detail are multirecord. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in details, then go back to record 3 of master and then the
onselectionchange trigger does not fire. The master tables "thinks" that record
three is the selected record while actually it should be record one which was the selected
record in the master table.
The correct behaviour should be that each table should "rember" it selected
record. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in detail, then go back to record 3 of master and the
onselectionchange of the master should fire so that details of master record 3 can be
shown. If you would have go back to record one of the master then not firing the
onselectionchange would be correct.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:18 a.m.
New subject: [JBoss JIRA] Updated: (RF-11060) onselectionchange working incorrect with two extendedDataTable on same page
[
https://issues.jboss.org/browse/RF-11060?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč updated RF-11060:
----------------------------
Fix Version/s: 4.1.0.Milestone3
(was: 4.1.0.Tracking)
Forum Reference: http://community.jboss.org/thread/167554 (was:
http://community.jboss.org/thread/167554)
onselectionchange working incorrect with two extendedDataTable on
same page
---------------------------------------------------------------------------
Key: RF-11060
URL: https://issues.jboss.org/browse/RF-11060
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-selects, component-tables
Affects Versions: 4.0.0.Final
Environment: GlassFish 3.0.1, Firefox
Reporter: Tom Giberius
Assignee: Lukáš Fryč
Priority: Critical
Fix For: 4.1.0.Milestone3
If you put two extendedDataTable A en B on the same page then the following goes wrong:
If you selected record one of Table A en then select record one from table B then the
onselectionchange trigger does not fire. The same counts for record two, three, etc.
This prevents me for building a Master-Detail data entry screen where both the master and
the detail are multirecord. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in details, then go back to record 3 of master and then the
onselectionchange trigger does not fire. The master tables "thinks" that record
three is the selected record while actually it should be record one which was the selected
record in the master table.
The correct behaviour should be that each table should "rember" it selected
record. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in detail, then go back to record 3 of master and the
onselectionchange of the master should fire so that details of master record 3 can be
shown. If you would have go back to record one of the master then not firing the
onselectionchange would be correct.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:41 p.m.
New subject: [JBoss JIRA] Resolved: (RF-11060) onselectionchange working incorrect with two extendedDataTable on same page
[
https://issues.jboss.org/browse/RF-11060?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč resolved RF-11060.
-----------------------------
Resolution: Duplicate Issue
Hi Tom, I have verified your sample and it works properly after fixing RF-11339, thus
I'm resolving this one as duplicated issue.
Thanks for the sample!
onselectionchange working incorrect with two extendedDataTable on
same page
---------------------------------------------------------------------------
Key: RF-11060
URL: https://issues.jboss.org/browse/RF-11060
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-selects, component-tables
Affects Versions: 4.0.0.Final
Environment: GlassFish 3.0.1, Firefox
Reporter: Tom Giberius
Assignee: Lukáš Fryč
Priority: Critical
Fix For: 4.1.0.Milestone3
If you put two extendedDataTable A en B on the same page then the following goes wrong:
If you selected record one of Table A en then select record one from table B then the
onselectionchange trigger does not fire. The same counts for record two, three, etc.
This prevents me for building a Master-Detail data entry screen where both the master and
the detail are multirecord. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in details, then go back to record 3 of master and then the
onselectionchange trigger does not fire. The master tables "thinks" that record
three is the selected record while actually it should be record one which was the selected
record in the master table.
The correct behaviour should be that each table should "rember" it selected
record. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in detail, then go back to record 3 of master and the
onselectionchange of the master should fire so that details of master record 3 can be
shown. If you would have go back to record one of the master then not firing the
onselectionchange would be correct.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4582
days inactive
4698
days old
richfaces-issues@lists.jboss.org
14 comments
6 participants
participants (6)
-
Brian Leathem (JIRA) -
Ilya Shaikovsky (JIRA)
-
Jay Balunas (JIRA)
-
Lukáš Fryč (JIRA)
-
Pavol Pitonak (JIRA)
-
Tom Giberius (JIRA)