Re: Understanding Wicket 1.5 page mapping

2011-04-23 Thread Alexandros Karypidis
Hello, Could you post some pseudo-code on what your request mapper looks like? I have a similar use-case but I wasn't able to follow. I created a MyRequestMapper class that wraps the default root mapper: setRootRequestMapper(new MyRequestMapper(getRootRequestMapper())); public

Re: Understanding Wicket 1.5 page mapping

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

Re: Understanding Wicket 1.5 page mapping

2011-04-23 Thread Alexandros Karypidis
Thx! On Sat, 23 Apr 2011 14:11:56 +0300, Alexandros Karypidis akary...@yahoo.gr wrote: Hello, Could you post some pseudo-code on what your request mapper looks like? I have a similar use-case but I wasn't able to follow. I created a MyRequestMapper class that wraps the default root

Understanding Wicket 1.5 page mapping

2011-04-22 Thread drewzilla80
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

2011-04-22 Thread Martin Grigorov
Hi, Create a new IRequestMapper and set it as root mapper - see the examples for HttpsMapper and CryptoMapper to see how. This new mapper will process the URL and decide which page to use (CategoryPage vs. LocationPage) and use BookmarkablePageRequestHandler to render it. The new mapper should

Re: Understanding Wicket 1.5 page mapping

2011-04-22 Thread drewzilla80
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

2011-04-22 Thread drewzilla80
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,

Re: Understanding Wicket 1.5 page mapping

2011-04-22 Thread Martin Grigorov
Ignore this. getRootRequestMapperAsCompound() will convert it for you anyway. Just follow how Https and Crypto mappers work On Fri, Apr 22, 2011 at 1:54 PM, drewzilla80 andrew.eas...@gmail.com wrote: Martin, Just playing with the code now - I'm afraid I'm not sure exactly what you mean by:

Re: Understanding Wicket 1.5 page mapping

2011-04-22 Thread drewzilla80
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: