Re: AuthenticatedWebSession.authenticate() not being called

I've moved one step forward: the authenticate() method now gets called if I use the SignInPage class included in wicket-auth-roles instead of my own SignInPage. However, as you can see in the code I posted yesterday, my SignInPage is very simple and, compared to the one bundled with wicket, it

Re: The order of setting mountPage and cryptoMapper changes behavior.

Hi, This is by design. This way you can encrypt the urls for some pages (the ones mounted before making CryptoMapper as the root one), and leave unencrypted the urls for the pages mounted after the CryptoMapper. Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On

Re: AuthenticatedWebSession.authenticate() not being called

Irrespective of the UI, have your read through http://wicket.apache.org/learn/projects/authroles.html ? Most likely the wicket-auth-roles login page is using one of the documented annotations that makes all the difference for you. Try to place that annotation on your page (I haven't read your

Re: Foundation integrated in wicket

Hi, I have something boiling at https://github.com/iluwatar/wicket-foundation. It is still in quite early stages but progressing nicely.. Best regards, Ilkka Seppälä -- View this message in context:

Re: on session expiry home page links behave differently than non home page links

Hi Satish, The problem here is that your quickstart uses the same page for page expired error and error 404. PageExpired.STATUS_CODE is 404. Your web.xml sets the 404 error page to /404, and you mount the PageExpired page as /404. You also set the PageExpiredErrorPage to PageExpired.