Eelco Hillenius wrote: > > But as you got from the answers on this thread, URL based > authorization schemes in not something we recommend for Wicket. It'll > basically bring you back to page-level development again, whereas the > whole point of Wicket is to provide a component based paradigm. >
Thank you all for help. The most helpful was the idea to put behind security constrains the login page only and use wicket authorization, that's what I did. Will it be ok if I try to write something to wiki? -- View this message in context: http://www.nabble.com/Authentication-Tomcat-%3C-%3E-Wicket-tf2588672.html#a7283196 Sent from the Wicket - User mailing list archive at Nabble.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 Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
