-
1. Re: datascroller issue
freakwave10 Jan 17, 2009 5:02 PM (in response to freakwave10)I solved most part of the issue.
The problem was that the backing bean was not in the conversation scope.
Still there is one strange behavior:
Lets say I am on page 3 of the list, and then I enter something new in my search field.
The ajax call is calling initDataScroller() and the List page is on page one. Great so far.
But when I click on the Next Page icon of the datascroller, nothing happens. Only on the seond click I will get the second page.
When I check the datascrollers page attribute value binding (page="#{displayPage}") I see:
- on the first click, only the setter is called
- on the second click the setter and then the getter is called
Could this a jsf lifecycle problem which I do not get? Why is only the getter called on the first click?
Kind regards,
Wolfgang -
2. Re: datascroller issue
nbelaevski Jan 18, 2009 9:49 AM (in response to freakwave10)Hi Wolfgang,
"freakwave" wrote:
Can you please clarify what is called on the first click: getter, setter or both?
- on the first click, only the setter is called
- on the second click the setter and then the getter is called
Could this a jsf lifecycle problem which I do not get? Why is only the getter called on the first click? -
3. Re: datascroller issue
freakwave10 Jan 20, 2009 12:11 PM (in response to freakwave10)Hi nbelaevski,
It is only the setter that is called on the first click.
On the second click it is the normal cycle, first setter and then the getter.
Kind regards,
Wolfgang -
4. Re: datascroller issue
ilya_shaikovsky Jan 23, 2009 10:58 AM (in response to freakwave10)<h:form> <rich:datascroller align="left" for="carList" maxPages="20" page="#{dataTableScrollerBean.scrollerPage}" reRender="sc2" id="sc1" /> <rich:spacer height="30" /> <rich:dataTable width="483" id="carList" rows="10" columnClasses="col" value="#{dataTableScrollerBean.allCars}" var="category"> <f:facet name="header"> <rich:columnGroup> <h:column> <h:outputText styleClass="headerText" value="Make" /> </h:column> <h:column> <h:outputText styleClass="headerText" value="Model" /> </h:column> <h:column> <h:outputText styleClass="headerText" value="Price" /> </h:column> <h:column> <h:outputText styleClass="headerText" value="Mileage" /> </h:column> </rich:columnGroup> </f:facet> <h:column> <h:outputText value="#{category.make}" /> </h:column> <h:column> <h:outputText value="#{category.model}" /> </h:column> <h:column> <h:outputText value="#{category.price}" /> </h:column> <h:column> <h:outputText value="#{category.mileage}" /> </h:column> </rich:dataTable> <rich:datascroller align="left" for="carList" maxPages="20" page="#{dataTableScrollerBean.scrollerPage}" id="sc2" reRender="sc1" /> <a4j:commandLink value="reset" ajaxSingle="true" reRender="sc1,sc2"> <a4j:actionparam value="1" name="page" assignTo="#{dataTableScrollerBean.scrollerPage}"></a4j:actionparam> </a4j:commandLink> <a4j:commandLink value="reset2" ajaxSingle="false" reRender="sc1,sc2"> <a4j:actionparam value="1" name="page" assignTo="#{dataTableScrollerBean.scrollerPage}"></a4j:actionparam> </a4j:commandLink> </h:form>
It works fine for me with both links.. :( Maybe you able to share your sample?