On 8/18/07, Mark Helmstetter <[EMAIL PROTECTED]> wrote:
> There's still a lot that's going on here that I don't quite understand,
> but most of that is due to my lack of understanding of how all of the T5
> IoC magic works. I'd really prefer to have a bit more control over how
> the Acegi classes are configured, and to do so using a more
> "traditional" Spring-based approach. I managed to do this for the
> injection of the UserDetailsService by omitting the binder.bind() call
> in the AppModule. I was unable to do this with the
> daoAuthenticationProvider, resulting in the error "Service id
> 'daoAuthenticationProvider' has already been defined.". It looks like
> I'd need to modify the SecurityModule to do this.
The binder.bind() is only for simple services that doesn't need any
special parameters such as constructor or properties set before use.
You can always create a build method for your object where you provide
the information you need, such as the buildUserInitializer. Also, when
I look at the code now, I think it's a double declaration of
UserDetailsService as I use it with both binder.bind() and a
buildUserDetailsService. :-)
> Overall though, I'm really happy with it, and thanks to you and Ivan for
> your contribution.
Thanks!
--
regards,
Robin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
