Hmm.. The current application of mine has a fairly non-trivial page-flow
and to me, wicket is absolutely sufficient at navigating.
Each page instance I need is passed to another page in contructor and
navigating back is a matter of setResponsePage and setRedirect.
(In fact, the programatical approach of wicket seems to me much more
elegant that declarative aproach from spring web flow for instance.
But it may only be personal preference.)
-Matej
Eelco Hillenius wrote:
Btw. what do you mean by page navigation options? Is there a thread or
feature request I could take a look at? Sounds interesting to me :)
-
Not really a recent discussion anymore.
Basically, people asked to have an easier way of accessing other pages
in the session, like navigating back to the last page. Thing with this
is though, that providing anything more than we do now can be dangerous,
as pages do not have to be in the session anymore...
Eelco
-------------------------------------------------------
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-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
-------------------------------------------------------
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-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
