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:50:15 GMT
By reinventing I was talking of , connection pool / management, transaction
management etc etc. I agree, you could do without spring and you could do
without Ibatis too, You do without Struts and just use servlets. You could!
But do u ? In an overall persona, Spring gives u great leverage. Ibatis to
Spring is probably not the right parameter to judge Spring. I am not Spring
crazy too. But I def feel It is better way to code and it does save a lot of

I am guessing you havent implemented Spring in a full fledge project. I was
assuming it aint gonna work and it would be a waste of time too before my
first Spring project. But just when the project was half way, i did realise
its benefits.  It is a good tool and am reiterating again, to see if it is
the right tool for you currently and going forward in your project, you
should be the one to decide.

I am sorry to say, I dont feel this is the right forum to talk about Spring
any more and I feel there would be better answers if you posted the same on
the Spring forum too.

Good luck with your project!


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

> On Mon, Jan 12, 2009 at 4:08 PM, Sundar Sankar <fatboysuns@gmail.com>
> wrote:
> > 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.
> iBATIS gets the properties file for you. There is no "reinventing." :
> <sqlMapConfig>
>    <properties resource="database.properties"/>
> I'm not trying to be a jerk, but I am curious what you are truly
> gaining using Spring. I'm not anti-spring but use it where it gives
> you an advantage. What true advantage are you gaining using it? (I do
> see some places where Spring really helps (hard-core test driven
> development) but I'd be willing to bet 90% or more are using Spring
> without TDD in mind and they would have saved time not even using
> Spring in the first place.)

View raw message