Hello, I found that the previous version of wicket and spring security integration require the Wicket-auth-roles in order to get them work together. Is this also a requirement for the new version of spring security 3 and wicket 1.5 to use Wicket-auth-roles? Or can we simply use Spring Security 3
I have not used it, but doesn't it stand to reason that it is simpler to decide whether a user can access a certain piece of code in Wicket. That being, because I would presume you can apply the spring security to panels or pages etc... based in wicket, and not spring filters etc Or perhaps I
I found example of Spring Security 3 and Wicket using wicket-auth-roles here https://cwiki.apache.org/WICKET/spring-security-and-wicket-auth-roles.html But I wonder why we need to use wicket-auth-roles to use Spring Security 3 with Wicket? -- View this message in context:
Technically, you don't *have* to use it. You can roll your own if you want. It's just much easier with auth-roles, because you have something to start with. On Thu, Feb 3, 2011 at 10:33 PM, ookpalm ookp...@gmail.com wrote: I found example of Spring Security 3 and Wicket using
Hello Thanks both of you. I got the idea. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Does-Wicket-1-5-requires-Wicket-auth-roles-if-I-want-to-use-Spring-Security-3-tp3259415p3259473.html Sent from the Users forum mailing list archive at Nabble.com.