thanks Martijn, I was looking at someone's else code and it was : params.add(PROJECTID, info.getId().toString()); setResponsePage(new =ProjectPage(params));
rather than: params.add(PROJECTID, info.getId().toString()); setResponsePage(ProjectPage.class, params); Need coffee. Sorry about that. Thanks for the pointer to wicket-annot - looks interesting Another question if you don't mind? Quite often we have a bookmarkable page with a form or link on it. This form/link will update the model and redisplay the current page. When this happens we loose the bookmarkable url. At the end of the onSubmit, or onClick we don't call setResponsePage. Should be call setResponsePage to get the bookmarkable url? On Wed, Feb 9, 2011 at 10:10 AM, Martijn Dashorst <[email protected]> wrote: > On Wed, Feb 9, 2011 at 9:37 AM, Wayne W <[email protected]> wrote: >> 2- is there a better strategy to having all url's bookmarkable >> (providing the page supports pageparamters)? Are there any changes in >> wicket 1.5 to make life more easy? > > Default constructor or constructor with pageparameters: you can take a > look at wicket-annot from wicketstuff core > > Martijn > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
