Quoting Ray Krueger <[EMAIL PROTECTED]>:
> You currently
have an AuthenticationDao that successfully returns a
> UserDetails
instance that is built up by your four database scheme
> now, correct?
The whole point of the AuthenticationDao is to build a
> UserDetails
instance, by whatever means necessary. So, no, users like
> you should
do exactly what you're doing. I don't see a reason for you
> two
implement a new AuthenticationProvider, unless the
>
DaoAuthenticationProvider is not meeting you're needs.
OK, thanks, I'll stick with this approach then, but at that rate AuthenticationDao most certainly belongs in the Service layer. No way I'd want to grab the user's info from multiple sources, let alone record their authentication in an audit log without wrapping a transaction around the whole unit of work.
I think it again really comes down to whether AuthenticationDao's name is bothersome enough to be worth changing at this time.
Scott
