You have to setup your mapper as root and keep the old root mapper as a delegate. See https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/protocol/https/HttpsMapper.java?source=c#L54
If your mapper resolves a page for the current url then return RenderPageRequestHandler(new PageProvider(SomePage.class)). If there is no match then use the delegate to resolve it. See https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/protocol/https/HttpsMapper.java?source=c#L92 Martin Grigorov Wicket Training and Consulting On Tue, Jan 28, 2014 at 4:52 PM, armandoxxx <armando....@dropchop.com>wrote: > Hey ... > > sorry but I don't understand > > the problem is that chain property in custom mapper is set upon > initialization in application class and it sets page .. > getRootRequestMapperAsCompound().add(new LocaleFirstMapper(new > MountedMapper("/localized", LocalizedPage.class))); > > I'm trying to figure out how to do this in custom IRequestMapper > implementation since my Page Class will change on each request ... > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/How-to-resolve-page-from-url-part-without-hardcoded-mapping-in-application-class-tp4663992p4663997.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
