Philip, > But I know the values are stored in the session pagemap, so I'd like > to be able to get them from there. I was hoping that a combination > of a bookmarked url, and maybe cookie or hidden field, managed > by wicket, would be enough for wicket not to stray from my 'nice' > bookmarked url, and not to expose wickets inner workings via a > url.
You got me really curious with this. I can't really help you, but now I really want to know more about this. I checked out the request lifecycle and found this page when googling: http://www.wicket-wiki.org.uk/wiki/index.php/Lifecycle What I'm trying to figure out is where Form.onSubmit() fits in, since this is where you determine the page that you redirect to, and logically (to me) this is where the URL of the next page gets set up. What I can't figure out here is this: when the form's submit button gets pressed on the current page, obvious a new HttpServletRequest gets sent to the server, and the onSubmit() method gets invoked. 1. What URL is sent to the server? 2. Since the response can differ according to the input of the form, this means that the URL could change according to the input... but the URL is already decided on in step 1 Obviously, there's something I'm not getting here. (Euhhhh, experienced Wicket people: feel free to step in any time ;-) In any case, once we can understand this lifecycle issue, we'll be able to figure out whether or not you can achieve what you're trying to do. Regards, David ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
