I got this interesting question regarding the cd app example.
Basically, the usual point of entry for editing is via the search page. So, if I'm done editing (save or cancel), I want to go back to the search page, with the same search and selected page within the results.
I solved this the most efficient and easiest way: I just store the search page in the session with a special key, and use that to navigate to when I'm done editing. To avoid that the search page is marked expired/ removed from the page list in the session after a few edits, I use the removeNewerThan method in session.
My question to you: do you think this is the right way to do things, or can you come up with a more elegant pattern? Offcourse, I could send all needed parameters to the search page, and then re-create the search/ selected results page using that. But that would be less efficient and would require much more programming while not adding anything to the business functionality (it's a navigation thing only).
Eelco
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
