Martin,
Thank you, I got the basics working with Jetty Wicket Filters.
LocaleFirstMapper was a better starting point instead of
PageInstanceMapper.
Cheers,
Eric Gulatee
On Tue, Jul 23, 2013 at 3:42 AM, Martin Grigorov mgrigo...@apache.orgwrote:
Hi,
I think the cleanest approach is to
Hi,
I think the cleanest approach is to create your own IRequestMapper and set
it as root mapper.
See
https://cwiki.apache.org/confluence/display/WICKET/Request+mapping#Requestmapping-CryptoMapper
and
HttpsMapper to understand what root mapper is.
Also see
Hi fellow Wicketeers,
We are in the process of upgrading a 1.4.X application to 1.5.X
We had 2 different URL 'contexts' within the same Wicket 1.4 Application.
/protected/*
All pages annotated with security. [In order to use J2EE security, LTPA,
Kerberos etc]
/*
All unprotected pages
Some more details,
Using a quickstart, If I replace the pageinstancemapper by a
custompageinstancemapper which does nothing else than extending
pageinstancemapper, I am getting pageexpiredpages.
This matches the kind of behavior I get when I add a second
pageinstancemapper mapping to another
