Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.1-Beta2
-
Component/s: Sample Apps
-
Labels:None
-
Environment:IF 2.1, Comp Suite
-
Assignee Priority:P1
Description
http://localhost:8080/comp-suite/showcase.jsf?grp=aceMenu&exp=dataTableSelector
When using the "ajax" selection option, the "status" panel group on the page is to be immediately updated with the details of the currently selected row objects. This doesn't happen, however refreshing the page renders the page as we would expect to have had following the updates.
When using non-ajax selection, the no behaviour on selection is expected, and to compensate an update button is added to the page. This button has execute @all render @all set, and updates the contents of status as expected.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
According to the class hierarchy of the datatable, it extends UIData which implements NamingContainer.
Since a datatable is a naming container and the "status" panel is outside of the datatable, the find algorithm might not be able to located it just by using "status". The full client id is "j_idt116:status". In other words, because status isn't in the table, we can't locate it simply by using "status" if I understand the heuristics of findComponent JavaDocs correctly.
Interesting that this occurred now, but adding prependId="false" to the form, fixed the issue as expected.
My guess is this is a result of the Id generation refactor that the table received in order to fix table nesting.
Thanks Deryk
I tried making this change to the example markup and it appears to behave correctly:
Index: samples/ace/comp-suite/src/main/webapp/resources/examples/ace/dataTable/dataTableSelector.xhtml
===================================================================
— samples/ace/comp-suite/src/main/webapp/resources/examples/ace/dataTable/dataTableSelector.xhtml (revision 29224)
+++ samples/ace/comp-suite/src/main/webapp/resources/examples/ace/dataTable/dataTableSelector.xhtml (revision )
@@ -56,7 +56,7 @@
</h:panelGrid>
</h:form>
- <h:form>
+ <h:form id="rowForm">
<ace:dataTable id="carTableSingleRow"
value="# {dataTableSort.carsData}"
{dataTableSelector.stateMap}"
var="car"
@@ -64,7 +64,7 @@
stateMap="$
selectionMode="single"
dblClickSelect="#{dataTableSelector.dblClick}"
- update="#{dataTableSelector.instantUpdate ? 'status' : 'none'}"
+ update="#{dataTableSelector.instantUpdate ? ':rowForm:status' : 'none'}"
rendered="#{dataTableSelector.selectionMode eq 'single'}">
<ace:column>
<f:facet name="header">
@@ -123,7 +123,7 @@
stateMap="#{dataTableSelector.stateMap}"
{dataTableSelector.dblClick}"
selectionMode="multiple"
dblClickSelect="#
- update="#{dataTableSelector.instantUpdate ? 'status' : 'none'}"
+ update="#{dataTableSelector.instantUpdate ? ':rowForm:status' : 'none'}"
rendered="#{dataTableSelector.selectionMode eq 'multiple'}">
<ace:column>
<f:facet name="header">
@@ -182,7 +182,7 @@
cellSelection="#{dataTableSelector.singleCell}"
selectionMode="singlecell"
dblClickSelect="#{dataTableSelector.dblClick}"
- update="#
{dataTableSelector.instantUpdate ? 'status' : 'none'}
"
{dataTableSelector.instantUpdate ? ':rowForm:status' : 'none'}
+ update="#"
{dataTableSelector.selectionMode eq 'singlecell'}
rendered="#">
{dataTableSelector.multiCell}
<ace:column>
<f:facet name="header">
@@ -241,7 +241,7 @@
cellSelection="#"
{dataTableSelector.selectionMode}
selectionMode="#"
{dataTableSelector.dblClick}
dblClickSelect="#"
- update="#
{dataTableSelector.instantUpdate ? 'status' : 'none'}
"
{dataTableSelector.instantUpdate ? ':rowForm:status' : 'none'}
+ update="#"
{dataTableSelector.selectionMode eq 'multiplecell'}
rendered="#">
<ace:column>
<f:facet name="header">
We should avoid using prependId=false in the public sample apps. as most people will use the default (true), and using false can cause issues with portlets.
Removed use of prependId="false"
Using @all as the update parameter of the table "fixes" the issue, but only by causing an abnormally large update to the components in the form.
ex.
{dataTableSelector.instantUpdate ? '@all' : 'none'}update="#
"
This is promising to see, but highlights the oddity of the 'status' panelGroup update not working, consider it and the table are in the same naming container.