Thank you.

"You could work with the ASO in the relevant onSuccess method." - i wish i
could - my onSuccess method for my Login page is *not* being called b/c
tapestry-spring-security filter hijacks the request to that url. Once
spring-security's filter (and it is not a Tapestry's filter) start
processing the request, i need to be able to do something with the ASO. 

Currently I am planning to subclass
org.springframework.security.ui.webapp.AuthenticationProcessingFilter and
overwrite onSuccessfulAuthentication method to create ASO. In order to do
that I need reference to ApplicationStateManager. However, i can't figure
out a way of how to get it except for a very ugly one:

1. I create a TapestryExposer eager service, which on construction,
remembers ApplicationStateManager passed to the constructor and set itself
into a Spring-defined bean called 'TapestryExposerHolder'
2. in my custom spring-security filter's (non-tapestry filter)
onSuccessfulAuthentication method I lookup TapestryExposerHolder, and from
it get TapestryExposer, and from that I get ApplicationStateManager.
ugrhhhh.

I anyone can come up with a cleaner way of doing something with ASO after
successful authentication by spring security, it is really appreciated.

R.
-- 
View this message in context: 
http://www.nabble.com/tapestry-spring-security%3A-how-to-set-ASO-on-successful-login--tp20865863p20874204.html
Sent from the Tapestry - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to