Renderer difference

Hi

I have spent a couple of hours to make a result pagination in jsf.

<h:commandLink actionListener="#{goodbyeBean.prev}" >

<h:outputText value="prev" rendered="#{goodbyeBean.pageNo > -3}"/>

<f:param value="#{goodbyeBean.pageNo - 1}" name="pageNo"/>

</h:commandLink>

<h:commandLink actionListener="#{goodbyeBean.next}">

<h:outputText value="next" rendered="#{goodbyeBean.pageNo < 0}"/>

<f:param value="#{goodbyeBean.pageNo + 1}" name="pageNo"/>

</h:commandLink>

goodbyeBean is a request bean. On the first page i hide next link and then when pageNo = -3 i hide prev link.

I have spent so much time and finally found solution for hiding links- which i present above. In a first turn, i had render attribute set to commandLink tag, i.e.

<h:commandLink actionListener="#{goodbyeBean.next}" rendered="#{goodbyeBean.pageNo < 0}">

<h:outputText value="next"/>

And i had a real problems with next link. On the first page i had a chance to click on prev - which is ok. When the page was redispalyed next link appeared, but if i clicked it , goodbyeBean.next function wasn't fired.

Update Model phase was reached cause i saw a new value in pageNo http request parameter but that's all.

If i clicked prev link twice and then click next everything seems to be ok and goodbyeBean.next is fired. But this time i should also be able to click on next again (i had clicked prev twice before) but goodbyeBean.next isn't fired again after the second next click.

I found solution in one of the example but can anyone explain me this weird behaviour ?

[1712 byte] By [milucha] at [2007-10-2 4:31:09]