All wicket runtime authorization is done in Component before anything
interesting happens:
public Component(final MarkupContainer<?> parent, final String id, final
IModel<T> model)
{
setId(id);
this.parent = getRealParent(parent, id);
getApplication().notifyComponentInstantiationListeners(this);
The instantiation listener(s) do the authorization. This is a particularly
strong guarantee since you cannot construct a Component any checks in the
instantiation listeners taking place.
Carfield Yim-2 wrote:
>
> According to the example AnnotationsPanelsPage.java , look like I just
> setup the role at user object and it will read the Annotations for the
> permission.
>
> Just wonder is the Annotations only for the class extending wicket API
> like WebPage and Panel or it will work for all objects running at that
> VM?
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Wicket-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wicket-user
>
>
--
View this message in context:
http://www.nabble.com/Question-about-wicket-auth-roles-tf2924973.html#a8186948
Sent from the Wicket - User mailing list archive at Nabble.com.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
