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
misunderstand spring security method of checking user permissions on

Just my guess, but like I said, I know close to nothing on the topic, I only
perused it once a while ago.

View this message in context: 
Sent from the Users forum 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

Reply via email to