I'm not in favor of this proposal. A framework should watch out not to a kitchen sink for everything you can image. You give the example of page parameters now. But what about constructor arguments in general? What about the model?
There are many ways in which the generic strategy would not be sufficient. In think we should keep it simple and focussed like it is now; the authorization strategy pattern works for declarative use. If you want to do stuff that is a lot more complex than that - i.e. relies on logic that involves instance variables and constructor arguments - you should seek for custom patterns. It shouldn't be hard to even combine this: use the generic strategy for declarative authorization, use specific logic - e.g. hidden in a base class - for specific more complex case, and let them both rely on a common set of business rules (e.g. implemented in some service). IComponentInstantiationListener is simply not equipped for passing in constructor arguments and I don't think we should extend it to include that (if that would be possible at all). An alternative here is to forget about the listener at altogether, but instead rely on AOP. I would be very interested in reading an article that displays how to do that with Wicket :) Eelco ------------------------------------------------------------------------- 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-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
