Hi,

There is a ticket with similar symptoms:
https://issues.apache.org/jira/browse/WICKET-5326
I think the most easier way is to extend CryptoMapper and call
super#mapHandler() only for IPageClassRequestHandlers for pages in a
whitelist. E.g. you can annotate them.


On Thu, Oct 3, 2013 at 3:09 PM, Roman Grigoriadi <[email protected]
> wrote:

> Hello Wicket users!
>
> I am trying to make a CryptoMapper working for a mounted page, in a way,
> that the URL in browser would be unencrypted, but all the other stuff like
> ListenerInterface links urls will be encrypted.
>
> I am using a wicket 1.5.10, but I tried to reproduce it on a quickstart
> project with 6.10.0 and it behaves the same, which is - "MountedMapper
> generates urls for all components and CryptoMapper is skipped"
>
> /The question is: is it an intended behavior in case of MountedMapper?/
>
> Here is a bit of code:
>
> //Applications init:
>
> setRootRequestMapper(new CryptoMapper(getRootRequestMapper(), this));
> mountPage("/nice/nicer", BookedPage.class);
>
> First line sets CryptoMapper as root with wrapped SystemMapper.
> Second internally sets *CompoundRequestMapper as root* with first in
> collection CryptoMapper and second MountedMapper.
>
> Now when i enter "localhost/nice/nicer" in browser url, a BookedPage is
> being rendered, and when it renders its only component - AjaxLink, it asks
> for an URL for its ListenerInterfaceRequestsHandler. As a root mapper,
> CompoundRequestMapper asks first a MountedMapper and as it gets an URL from
> it, CryptoMapper is never asked to encrypt it after.
>
> I figured out to use a CustomMountedMapper and return null in
> mapHandler(..)
> for all handlers, but the RenderPageRequestHandler, but it doesn't feel
> being correct to me.
>
> Greetings, Roman.
>
>
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/CryptoMapper-and-mounted-pages-tp4661676.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to