Hi, In my project we often have the case where a user initially is allowed to construct a certain component (pages mostly) but whether he really can depends on the model of the page. So my request / suggestion is to enhance IAuthorizationStrategy with the following method isInstantiationAuthorized(Class, IModel). whether this methods is made available next to isInstantiationAuthorized(Class) or replaces it is not important.
As far as i can see the following changes need to be made -Application.notifyComponentInstantiationListeners needs to be upgraded to receive the model to, or the component should not call notify untill the model has been set on the component (which happens on the next line) -the default listener needs to pass the model to the strategy. For regular models this should not be a problem but IWrapModels might have a problem when accessing anything else from the component but the id. Not passing the wrappedmodel but the original model is imo not an option because the main point of passing the model is to be able to use the getObject method. What do you think? Maurice ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
