Hi,
I think the IndexedParamUrlCodingStrategy in Wicket and the way you use it
is really nicely done.
I have set up one as follows:
mount("/item", new IndexedParamUrlCodingStrategy("/item", ItemViewPage.class
));
1) From looking at the above, the mount path appears to be redundant. Is
there any particular reason, and I would really like to understand the
Wicket API and design better.
2) The bookmarkable link is working fine e.g. /mycontext/app/item/FOO123
But now, when a user navigates away to some "normal" Wicket pages, the URL
persists in the browser address bar and looks like this for e.g.:
/mycontext/app/item/FOO123?wicket:interface=:11:::
Is there any way to switch back to the normal
/mycontext/app/?wicket:interface=:11:::
Thanks,
Peter
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
