By the way, you don't *have* to implement your UserDetailsService
inside a Spring container. You can do so, but you lose the easy
ability to have other HiveMind services automatically injected into
your implementation instance. Since you're just implementing an
interface, I really see no need to have it as a Spring bean (I don't
use the Spring container at all in my applications, though, so I am
biased I guess). To do it using HiveMind, you'd use the
BuilderFactory (the default) to build your implementation object
rather than the SpringLookupFactory.
On 1/22/07, Jesper Zedlitz <[EMAIL PROTECTED]> wrote:
Thiago H de Paula Figueiredo wrote:
> What do I do if I want to use tapestry-acegi leaving the acegi
> configuration in spring instead of HiveMind?
>
You have your own org.acegisecurity.userdetails.UserDetailsService and want
to use it with tapestry-acegi? No problem!
Here is an example how to do it. First we need a Spring bean for that
UserDetailsService (in your applicationContext.xml)
<bean id="userDbAuthenticationDao"
class="jesper.UserDetailsServiceImpl"
name="authenticationDao">
<!-- whatever your implementation needs -->
</bean>
(That replaced the "memoryAuthenticationDao" from my example.)
We reference this bean in hivemodule.xml
<implementation service-id="hivemind.acegi.dao.UserDetailsService">
<invoke-factory service-id="hivemind.lib.SpringLookupFactory">
<lookup-bean name="authenticationDao" />
</invoke-factory>
</implementation>
Jesper
--
Jesper Zedlitz E-Mail : [EMAIL PROTECTED]
Homepage : http://www.zedlitz.de
ICQ# : 23890711
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
