"start" not called for Custom Login Command

Question

Hello,
I'm working on getting acegi to handle the authentication instead of the app server. So I extended AppServerLoginCommand and overrode doAuthenticate and "start". But "start" never seems to get called; neither during initialization of the server nor before or after doAuthenticate is called. Note that doAuthenticate *does* get called, so BlazeDS does know about my custom command. I tried implementing just LoginCommand instead of extending AppServerLoginCommand but the same result.
The reason I need start is because I want to grab the WebApplicationContext and from there get the authenticationManager bean so that doAuthentication can do its job.
I noticed that "stop" never gets called either.
Any pointers or clues would be appreciated.
/r

Answer 1

I looked through the source code and as best I can tell "start" never gets called for LoginCommand. This is, by no means, a certainty since I only partially followed the stack trace and looked at the source near the place where the LoginCommand gets created, so there may be another point in the lifecycle where start gets called. But anyway, if you look at the file at:
http://opensource.adobe.com/svn/opensource/blazeds/trunk/modules/core/src/java/flex/messag ing/config/MessagingConfiguration.java
near
private LoginCommand initLoginCommand(LoginCommandSettings loginCommandSettings)
you'll notice that the LoginCommand gets created but start is not called.