Hi folks,
Timothy Bennett and I have been thinking about how to hook Guardian
(http://guardian.safehaus.org), a simple authorization API into Wicket
so we can *declaratively* control the visibility of components on
pages. More complex interactions though where you alert the user about
their
Sounds nice!
The first thing you should look at is the interface
IAuthorizationStrategy. Then, look at wicket-auth-roles and
wicket-auth-roles-examples. This is a basic example implementation,
based on annotations and the metadata facility we've silently had in
Wicket for some time. They are
Eelco Hillenius wrote:
Sounds nice!
Thanks for the rapid response.
The first thing you should look at is the interface
IAuthorizationStrategy. Then, look at wicket-auth-roles and
wicket-auth-roles-examples.
This is a basic example implementation,
based on annotations and the metadata