Hi all Wicket users.
While I was trying to design a wicket app in my mind - the first thing
I thought of was authentication and ( spring ) security.
I know that wicket is secure by default ( a quote from wicket
features? :), we can use wicket auth annotation based security.
Wicket will
It all depends on your needs ;-). I don't know much about Spring
Security, but personally speaking I've always been fine with Wicket
authentication.
While I was trying to design a wicket app in my mind - the first thing
I thought of was authentication and ( spring ) security.
I know that
http://javajeedevelopment.blogspot.com/2011/03/integrating-spring-security-3-with.html
2011/9/19 Andrea Del Bene adelb...@ciseonweb.it
It all depends on your needs ;-). I don't know much about Spring Security,
but personally speaking I've always been fine with Wicket authentication.
While
You're taking the statement Wicket is Secure by default out of its
context. The full statement is Wicket is secure by default. URLs do not
expose sensitive information and all component paths are
session-relative. Explicit steps must be taken to share information
between sessions. Furthermore URL
