[richfaces-issues] [JBoss JIRA] (RF-11434) datascroller broken in 4.1.0.M1
[
https://issues.jboss.org/browse/RF-11434?page=com.atlassian.jira.plugin.s...
]
Brendan Healey commented on RF-11434:
-------------------------------------
I now realise that this issue was caused by the fact that I'd turned partial
state saving OFF on the view in question with this context parameter:
<context-param>
<param-name>javax.faces.FULL_STATE_SAVING_VIEW_IDS</param-name>
<param-value>/secure/myView.xhtml</param-value>
</context-param>
I just tested on 4.1.0.M2 and with partial state saving enabled the datascroller
works ok, with it disabled it doesn't.
I was turning partial state saving off to use 'dynamic ui:include', due to a
known mojarra bug/restriction. Because of the complications I've stopped using
this approach.
So datascroller is working ok for me. I would suggest that perhaps it would be
prudent to make a call on whether or not full state saving is supported or not?
I don't know whether or not the position on this is already established. During
the test I carried out above, I noticed (out of the corner of my eye) a
selectionchange event not firing on an extendedDataTable with partial state
saving disabled, suggesting perhaps that there are multiple issues.
datascroller broken in 4.1.0.M1
-------------------------------
Key: RF-11434
URL: https://issues.jboss.org/browse/RF-11434
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-tables, regression
Affects Versions: 4.1.0.Milestone1
Environment: Mojarra 2.1.3
Reporter: Brendan Healey
Priority: Critical
Fix For: 4.1.0.Milestone4
I have an extendedDataTable with a datascroller. The first page of results
displays correctly, but on pressing the control for page 2 (or any other)
nothing happens. Using a4j:log I see that the ajax response to the post
request contains a java.lang.NullPointerException.
On reverting to 4.0.0.Final it works successfully. The problem also affects
a rich:dataTable. I've not been able to locate the M2 release in the Maven
repo to test it.
The extendedDataTable value attribute value is a straightforward List<Event>
where Event is a standard pojo. I was using ExtendedDataModel but removed
this code to eliminate this as a cause.
{code}
<h:form id="displayform" prependId="false">
<rich:panel>
<rich:tabPanel id="uppertabs" switchType="ajax"
itemChangeListener="#{manageEventsView.upperTabChange}">
<rich:tab id="list" title="#{msgs.listText}">
<ui:include src="manageEvents/list.xhtml"/>
</rich:tab>
...
{code}
{code:title=manageEvents/list.xhtml}
<a4j:log/>
<rich:extendedDataTable
id="eventlist"
rows="8"
value="#{manageEventsView.list}" var="var"
selection="#{manageEventsView.listSelectedRow}"
selectionMode="single"
style="display: block; white-space: nowrap">
<a4j:ajax render="eventlist lowertabs"
event="selectionchange"
listener="#{manageEventsView.listRowSelect}"/>
<rich:column style="text-align: center">
...
</rich:column>
</rich:extendedDataTable>
<rich:dataScroller for="eventlist"/>
{code}
Please let me know if I can provide any further information.
Regards,
Brendan.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira