Thanks for that kind suggestion, but I already have working SecurityWebApplication and SecurityWebSession implementations. And my problem was never a lack of code examples, but instead my problem was the need for so much boilerplate code in the first place. I get the feeling most of this code can be exactly the same for a lot of projects, and then it would be logical to have a shared base for all these projects, maybe as a part of SWARM/WASP, or wicket auth roles or wicket-shiro.
Regards /Jimi > I have a SpringSecurityWebApplication and SpringSecurityWebSession > class you can use if you want. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-security-what-are-the-best-options-Spring-Security-reached-almost-all-the-way-tp2068415p2068916.html Sent from the Wicket - User 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
