how about because of the fact we cant magically intercept instantiation before it happens without using some magic like managed aop container or load time/compile time bytecode instrumentation
-igor On Wed, Apr 30, 2008 at 11:35 PM, Ned Collyer <[EMAIL PROTECTED]> wrote: > > Why is isInstantiationAuthorized(Class componentClass) only called after > instantiation? > > eg, > isInstantiationAuthorized(component.getClass()) > > Been driving me crazy - u'd expect this to be called before instantiation. > > I'm curious because it's probably been done for a good reason. > -- > View this message in context: > http://www.nabble.com/Question-about-IAuthorizationStrategy-tp16993036p16993036.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
