You can navigate to a specific instance by e.g. passing a reference of
it to another page you want to view, and then setting that page as the
page to render again (setResponsePage). This is different from Tapestry,
which has 'logical' pages, but where state is made explicit. With Wicket
you can reuse the instance of the page you are working on, including all
it's instance data right away.
Eelco
And I'm still wondering how page navigation works :-( I read in
javadocs that when page gets instantiated, it is stored in user's
session. But what happens when same page gets instantiated mutliple
times? It happens when one goes to specific page with PageLink
component for eg.
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
