FWIW, I recently switched from using container-managed security (i.e.
JDBCRealm in Tomcat) to using Acegi Security and it's working great so
far. Not only is it portable between app servers, but it allows you to
easily plugin in your own authentication provider.
Matt
On Mar 17, 2005, at 8:24 AM, Brett Gorres wrote:
Brandon:
�
- ability to potentially switch db connection parameters in only�one
ibatis database.properties file�(don't repeat yourself)
�
- ability to change�your user auth data model in one ibatis XML file
instead of potentially multiple web.xml files
�
- wouldn't this�provide good "inversion of control" / "dependency
injection": if the realm implementation itself were configurable,
you'd presumably tweak that realm implementation in one place (if, for
example, you wanted to temporarily read in user information from an
XML�file�during db maintenance.)� Your ibatis realm implementation may
be a singleton used by more than one app--and you could get away with
configuring that�in only one spot if that's what floats your boat...
�
It seems worthwhile to me--in fact I had already considered doing
something like this...
But I wasn't using Tomcat at the time.� My only reservation is that I
would be more likely to develop and use something like this if it�were
made to be�portable across Java app servers.
�
Agree? Disagree?
�
-Brett
Brandon Goodin <[EMAIL PROTECTED]> wrote:
i don't see why you would need to use ibatis for that. If you wanted
to you could write a Realm implementation that took advantage of
ibatis... but, why?
Brandon
On Thu, 17 Mar 2005 15:37:03 +0000, Tim Christopher
wrote:
> Hi,
>
> Can anyone let me know if it is possible to use iBATIS for
> implementing JDBCRealm, or do I have to access the database directly?
>
> I've looked on Google and in the Developer Notes for iBATIS and have
> found nothing on this topic.
>
> Any help would be much appreciated.
>
> Tim Christopher
>
