you can pass in the page id obtained from page#getpageid() as a bookmarkable url, then to navigate back to the original page you can do setResponsePage(new PageReference(pageid).getPage())
this will, however, leave you on a nonbookmarkable url when you come back. if you want bookmarkable urls all the way around then you need to do what stateless frameworks do, pass the return url to the detail page as a parameter. -igor On Mon, Sep 17, 2012 at 3:07 PM, Nelson Segura <nsegu...@gmail.com> wrote: > Hello, > I have a very common pattern in which from a list, I can to detail of > an element in the list. > In the detail page I have a reference back to the page list. > The page list can be different, several list might point to the same detail. > Until now I have been using page reference to return to the previous > page, and it works well. > However, passing the page reference to the constructor of the detail > page, means that page is not bookmarkable (unless I am mistaking > something) > > Is there a way a can pass the page reference as a request parameter, > and so make the page bookmarkable? (ex. by using id, page map, etc). > Of course if no page reference can be retraced from the map, then we > just ignore the back reference. > > Any ideas? > > - Nelson > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
