ibatis-user-java mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sundar Sankar" <fatboys...@gmail.com>
Subject Re: iBATIS DAO vs SqlMapClientDaoSupport
Date Mon, 12 Jan 2009 21:08:25 GMT
Yes. Our project did take configurable prop files. But it didnt do just
that.  But looks like your need is to take a prop file and return an object
after hitting the db the prop file points to. Spring wouldnt be neccessary
if thats your used case.

But I personally wouldnt wanna reinvent the wheel and waste time and money
on writing code and more so on testing the same for something that is
already available and well tested.


On Mon, Jan 12, 2009 at 1:23 PM, Rick <rickcr@gmail.com> wrote:

> On Mon, Jan 12, 2009 at 2:44 PM, Sundar Sankar <fatboysuns@gmail.com>
> wrote:
> >
> > The way I see it, Instead of packaging the daos and ibatis jars, You
> would
> > package the daos, and service and other jars together and make it
> reusable.
> > In one of my earlier projects, I had a central bootstrap, that was spring
> > based and that would be the one on deciding on what to call and how to
> call
> > which is where I used spring and still made my persistence layer,
> reusable.
> And what if your end client didn't wanted to create a central
> bootstrap that was spring based? How well would your daos work in your
> packsge then?
> In my case I can say "Hey use this jar. Just provide your
> database.properties file in your classpath." Done.

View raw message