The userCache is not injected into UserManager, only UserSecurityAdvice. It's also used by Acegi and basically maintains a cache of the users. UserSecurityAdvice uses it to expire cache items when a user is updated. Now that we use our own Dao (instead of Acegi's), it may be possible to remove this and rely on Hibernate's 2nd level cache.
At the very least, this cache prevents Acegi from hitting the database for every request when the user information is not stored in the session (which is an option). Matt On 3/1/07, tonyl <[EMAIL PROTECTED]> wrote:
I haven't been able to find any clear explanations of the userCache - what it is, why use it, etc. And I really don't understand the purpose of having a userCache in 2 places. What's going on? Thanks, Tony -- View this message in context: http://www.nabble.com/Why-is-userCache-in-userManager-and-UserSecurityAdvice--tf3327560s2369.html#a9251684 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- http://raibledesigns.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
