On 8/30/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> exactly. iauthstrategy is geared more towards declarative security and more
> towards components not pages. if your usecase does not match then doing the
> check in the base page's constructor is the way to go - clean and simple.
> thats why we have all those RestartResponseAtFoo exceptions :)

Well the confusion started because all the sample code that does PAGE
authorization is build on top of IAuthStrat.

Wicket is pretty flexible and there are fortunately always multiple
ways to do things :-)


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
Wicket-user mailing list

Reply via email to