Wicket supports per component authorisation. You could take a look at
wicket-auth-roles-example (a small project available through svn).
In this project some components (pages) are marked. The mark indicates
which roles are required for the component. As long as the user does not
hit those components the application runs fine. As soon as the user does
hit such a component, the sign-in page is displayed.
Erik.
Dmitry Kandalov schreef:
> I want to define security constraints for tomcat authentication so that one
> part of my wicket application would be anonymously available and another
> not. So I guess I need different url's. What is the best way to do this?
> Should I make two different WebApplication's and map them to different url's
> or should I implement IRequestCodingStrategy?
>
--
Erik van Oosten
http://www.day-to-day-stuff.blogspot.com/
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
