component authorization piggy backs on component instantiation listeners:
public Component(final String id)
{
setId(id);
getApplication().notifyComponentInstantiationListeners(this);
as you can see, it is not called /after/ instantiation (although super
constructors will have run already), but during construction. i don't see
any alternative to this approach as components (including pages) can be
instantiated in wicket via the new operator. it's only at the second line
of Component's constructor above that we notify any component instantiation
listeners and one of those is an authorization listener. make sense?
Ned Collyer 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-tp16993036p16995059.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]
