Future of Pax Wicket, part 2.
About a week ago, I introducede enough changes to start supporting
Authentication. AbstractContentSource, AbstractAggregatedSource and
AbstractPageFactory received a protected method to obtain the current user's
PaxWicketAuthentication object, which provides the username and the Roles
that this user has.
The pattern of usage is that the pax wicket client that creates the
PaxWicketApplicationFactory also calls the setAuthenticator() on the created
factory. We have at the moment only one PaxWicketAuthenticator implementation
provided, which is using the User Admin Service in OSGi. I guess over time we
can complement with more. So, the code of usage looks like;
PaxWicketApplicationFactory factory = new PaxWicketApplicationFactory(
bc, homepageClass, mountPoint, appName );
PaxWicketAuthenticator auth = new UserAdminAuthenticator( bc, appName );
auth.setAuthenticator( bc, loginPageClass );
IMHO, fairly simple and straight forward.
Cheers
Niclas
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
