Re: url after form submit with redirect

2008-08-21 Thread miro
Assume I passed my instance in setResponse() method , in this case wicket generates its own url basically from the session , so this means i cannot expect to have the mountpath url in case of instance in setResponse() method ? and only way to have themountpath in url is to pass

Re: url after form submit with redirect

2008-08-21 Thread Matej Knopp
Just mount the page with HybridUrlCodingStrategy. -Matej On Thu, Aug 21, 2008 at 3:50 PM, miro [EMAIL PROTECTED] wrote: Assume I passed my instance in setResponse() method , in this case wicket generates its own url basically from the session , so this means i cannot expect to have the

url after form submit with redirect

2008-08-20 Thread miro
After submit a form with redirect set to true , the wicket generates its own url and not the mountpath. Is there a way to avoid this ? -- View this message in context: http://www.nabble.com/url-after-form-submit-with-redirect-tp19069918p19069918.html Sent from the Wicket - User mailing list

Re: url after form submit with redirect

2008-08-20 Thread Erik van Oosten
Miro, In Nabble, please do not edit your message after you've send it. That way you're message appears twice. Wicket will always use the mount path of the page you are forwarding to, that is, if you called setResponsePage. You can also look into mounting with a HybrodUrlEncoder. Regards,

Re: url after form submit with redirect

2008-08-20 Thread miro
here is what i do In Application which is WicketApplication in the init method mount(new HybridUrlCodingStrategy(/secure/index.jas/searchPCR,Foo.class,true)); my form object the method onSubmit() calls setResponsePage(new Foo()); does this matter and setRedirect(true) and my web.xml wicket

Re: url after form submit with redirect

2008-08-20 Thread Jeremy Thomerson
This is covered in many responses in the archives of this list, and I'm sure the wiki, but anyway, here's the basics: If you create a new Page instance, and call setResponsePage(myInstance), Wicket must respond with *that exact instance.* This means that the URL needs to be a session-specific