You can even leave the definition of the daoAuthenticationProvider in place, add a new definition for your customeDaoAuthenticationProvider [or whatever you call it], and then switch back and forth while testing [or if appropriate, you can use both providers].
Nathan ----- Original Message ----- From: "John Kwon" <[EMAIL PROTECTED]> To: [email protected] Sent: Monday, October 29, 2007 12:34:27 PM (GMT-0800) America/Los_Angeles Subject: Re: [appfuse-user] Sample Code for Acegi CustomAuthenticationProvider So if I implement my own CustomAuthenticationProvider, and replace the entry for the daoAuthenticationProvider < bean id = "daoAuthenticationProvider" class = "org.acegisecurity.providers.dao.DaoAuthenticationProvider" > < property name = "userDetailsService" ref = "userDao" /> < property name = "passwordEncoder" ref = "passwordEncoder" /> </ bean > with my own class, (I'm looking at the code for DaoAuthenticationProvider), I should be able to drop mine neatly in? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
