Understanding Wicket 1.5 page mapping

Hi, I'm really keen to have a clearer understanding of the page mapping changes in Wicket 1.5 - right now it is still not totally clear in my mind. The best way to explain is by highlighting some requirements I have based on the URL scheme we are trying to achieve in a project. We have the

Re: Understanding Wicket 1.5 page mapping

Hey Martin. Thanks for the awesome reply speed! It is amazing how committed you guys are to solving the real world problems we face as developers. Wicket is such a cool framework and it's great to see these new features constantly evolving to add the sort of flexibility needed when there's an

Re: Understanding Wicket 1.5 page mapping

Martin, Just playing with the code now - I'm afraid I'm not sure exactly what you mean by: The new mapper should be compound (ICompoundRequestMapper) and fallback to default mappers for Wicket internal works (link/form listeners, ajax, ...) Could you elaborate briefly on this piece? Thanks,

mountPage(...) issuing a 302 redirect

I'm using Wicket 1.5-rc2 and have noticed that I'm getting what I believe to be unnecessary 302 redirects for bookmarkable/stateless pages. In my application.init(), I'm doing the following: mountPage(/myPage, MyPage.class) When I request this page in my browser at http://localhost:8080/myPage,

Re: Understanding Wicket 1.5 page mapping

Thanks, Martin. That's what I already ended up doing as it turns out (I dug into the code and noticed the method you specified). I've got my whole original use case working very nicely indeed - thanks for your help. dz -- View this message in context:

Re: Understanding Wicket 1.5 page mapping

Try creating a method such as this; private IRequestHandler renderPage(Class? extends IRequestablePage pageClass, PageParameters pageParameters) { PageProvider pageProvider = new PageProvider(pageClass, pageParameters);