Hi Stephane,
The reason for not using the WO caching mechanism was, that I'm maintaining a
application which has pageWithName methods ad infinitum and this method does
always create a new instance of a page (please do correct me, if this is not
true), which is not the behaviour I want it to
Can you explain this more in terms of the end result you're trying to
achieve rather the approach you're trying at the moment?
On Oct 14, 2009, at 4:03 AM, Andri vonAllmen wrote:
Hi Stephane,
The reason for not using the WO caching mechanism was, that I'm
maintaining a application which
The end result:
A user navigates from page A to page B to page C.
Page C has a hyperlink to page A (return pageWithName(A)).
If clicking on this hyperlink, page A shall be shown in the same state as it
has been left (e.g. the same filter options, etc.).
Mike Schrag msch...@mdimension.com
My recommendation is not to think of this in terms of preserving the
page instance, and instead think of it in terms of preserving the
underlying model state for the page and pass that around. Now you
COULD actually pass a previous page instance into the next page
instance so you come back
I have some cases where before returning the 'next' page, I store the
current page on a var on the next page, like 'previousPage'
nextPage=pageWithName(blabla);
nextPage.setPreviousPage(this);
Then on that page I have a link or button that returns previousPage.
return previousPage;
Seems
