Hi, I just touched CustomHomeMapper in Wicket 6.0 to support what you need. I think this way it is more usable in real life. See http://git-wip-us.apache.org/repos/asf/wicket/repo?p=wicket.git;a=commitdiff;h=cabc1bee6a5e3e43e58c9f4c7f8b5cda401c558a The new code of this class at: http://git-wip-us.apache.org/repos/asf/wicket/repo?p=wicket.git;a=blob;f=wicket-examples/src/main/java/org/apache/wicket/examples/requestmapper/CustomHomeMapper.java
Have fun! On Sun, Mar 18, 2012 at 7:55 PM, Girts Ziemelis <girts.zieme...@gmail.com> wrote: > I am doing the conversion from 1.4 to 1.5.5 and at the same time trying to > start using LocaleFirstMapper and CustomHomeMapper from wicket examples. > Everything works nicely except, I have a statefull home page and seems > CustomHomeMapper does not handle this case. Page renders fine, but Ajax > requests do not work. I think the reason is, because CustomHomeMapper does > not add the version number to the link, so the link stays /en, instead of > /en?0 like in case, if CustomHomeMapper is not used (home page link is /?0). > > Any easy solutions to fix this, before I start debugging wicket 1.5 request > handling, trying to understand how things work? > > BTW, nice work on 1.5 wicket team. Thanks :) > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
