you could maybe use the metadata of session to store it in a 'standard' wicket sessionjohanOn 11/13/06, Nick Johnson
[EMAIL PROTECTED] wrote:I want to be able to have a nice, clean implementation of one
authorization strategy for all of my applications such that once I'vesigned in for one
My rough plan was to create a concrete class implementing
IAuthorizationStrategy, a SignIn.java and corresponding SignIn.html. Then
in any application that needed authorization, I'd call
setAuthorizationStrategy and pass in an instance of my
SignInAuthorizationStrategy.
The problem is that
I want to be able to have a nice, clean implementation of one
authorization strategy for all of my applications such that once I've
signed in for one application, I'm signed in for all of them.
My rough plan was to create a concrete class implementing
IAuthorizationStrategy, a SignIn.java and
