Ryan Wynn wrote:
On 4/18/06, Richard Wallace <[EMAIL PROTECTED]> wrote:
The problem I'm running into is that when next or previous are clicked,
instead of the content for the next page being displayed,the content
from the first page is always displayed. I've checked by logic and made
sure the the value of [EMAIL PROTECTED] is what it
should be. The problem looks like the method getCurrentPage() is never
even called when the next/prev links are hit. I'm guessing it's because
clay is caching the results from the first time the page is loaded and
then just using that on subsequent requests.
Richard,
I was able to accomplish something similiar to what you are describing
but I had to have clay re-create the view on next/back.
protected void navigate(String viewId) {
UIViewRoot newView = FacesContext.getCurrentInstance().getApplication()
.getViewHandler().createView(FacesContext.getCurrentInstance(),viewId);
FacesContext.getCurrentInstance().setViewRoot(newView);
}
I'll defer to Gary on whether or not this is required.
Ryan
Is the viewId the dynamic page to be included or is it the base page
that includes the dynamic content? My situation is that I have a single
page, /report/default.html, and that is the only view that should ever
be the view root. Within that is all my headers and footers and stuff.
In the content area of that view I have the clay inclusion which uses
the backing bean to determine what to include based on the current
page. So, if I used your method above, would I just always create a
new root view of the /report/default.html view?
Rich
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
