Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user-java@ibatis.apache.org
Received-SPF: pass (athena.apache.org: domain of fatboysuns@gmail.com
 designates 209.85.146.182 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:references;
        b=dJHd46W/3QgumFKbNugbeeDQc4tdRzM85z0EVYrmtkRVKPDote/8XuIJjNBs2nRlg+
         l7RdLmgf1g9EmWD1byaBUgUvcyqwNXfbs6zOT1n1JGCrXJ/uqUhCbU76ENOUAjtxZGaP
         KuMDSRwyVb7ZTtAKU14faQ0Fv+XZJCzFB4mso=
Message-ID: <d4ebe7ab0901121442k642269e0hc7ba935b5049a11@mail.gmail.com>
Date: Mon, 12 Jan 2009 15:42:19 -0700
From: "Sundar Sankar" <fatboysuns@gmail.com>
To: user-java@ibatis.apache.org
Subject: Re: iBATIS DAO vs SqlMapClientDaoSupport
In-Reply-To: <535a60b10901121354m60c2d804r4d1360b2661029ca@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_13461_29338387.1231800139091"
References: <583d4dff0901090834l798e7e39k341a2ef652c5554f@mail.gmail.com>
	 <c593b8750901091125w27e0c10eo4eed3474d41a3dac@mail.gmail.com>
	 <29DE2E073DFD104182C9DDDF037555947AD938@server01.wh.lan>
	 <583d4dff0901120855m6f92f98csbec0e94651e60b5c@mail.gmail.com>
	 <d4ebe7ab0901121144k4403f94emba148e4ee809b28c@mail.gmail.com>
	 <583d4dff0901121223s2671a556ia6ae73ea046206d1@mail.gmail.com>
	 <d4ebe7ab0901121308i39f85314laa4f48b270f9e511@mail.gmail.com>
	 <583d4dff0901121321k7f5e8d8dga6dcc5fed5652d2b@mail.gmail.com>
	 <535a60b10901121354m60c2d804r4d1360b2661029ca@mail.gmail.com>

------=_Part_13461_29338387.1231800139091
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I guess I missed this one. But why do u need to use
applicationContext.getBean. Those are ancient man. With Spring Annotations
(check the 2.5+ documentation), U hardly need xmls and all of this crappy
code.
I am not sure if that and the need for those huge amounts of xmls worried u
about Spring as such. But Those were my $0.02 about the same.

-S

On Mon, Jan 12, 2009 at 2:54 PM, Chris O'Connell <
oconnell@gorillachicago.com> wrote:

> I have used Spring to configure multiple instances of the same set of DAO's
> to hit different databases.  Right there Spring has a huge advantage over
> having to hardcode a specific config file right into the code.  Also, using
> DI makes it easier to code against interfaces and let Spring worry about
> having to instantiate the correct instance of that interface.  You haven't
> indicated anything about who is actually going to be creating all the
> objects you will be needing.  I'm a big fan of the rule that code should
> either use an object or create it, but not both.  That doesn't necessarily
> have anything to do with iBatis, but Spring's DI certainly makes that
> easier.
>
> Once again, if Spring doesn't solve any of your problems, don't use it.
> But your reasons for not using it seem a little inconsistent.  You state
> that the only thing that Spring would do for you is allow you to use a
> Spring utility class.  But you then state that you don't want to use DI
> because you don't want clients of your API to depend on Spring.  Well, those
> things really are independent of each other.  I have nothing to gain by you
> using Spring, but you might want to take another look at what Spring really
> does before you decide you don't want to use it.
>

------=_Part_13461_29338387.1231800139091
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I guess I missed this one. But why do u need to use applicationContext.getBean. Those are ancient man. With Spring Annotations (check the 2.5+ documentation), U hardly need xmls and all of this crappy code. <br>I am not sure if that and the need for those huge amounts of xmls worried u about Spring as such. But Those were my $0.02 about the same.<br>
<br>-S<br><br><div class="gmail_quote">On Mon, Jan 12, 2009 at 2:54 PM, Chris O&#39;Connell <span dir="ltr">&lt;<a href="mailto:oconnell@gorillachicago.com">oconnell@gorillachicago.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I have used Spring to configure multiple instances of the same set of DAO&#39;s to hit different databases.&nbsp; Right there Spring has a huge advantage over having to hardcode a specific config file right into the code.&nbsp; Also, using DI makes it easier to code against interfaces and let Spring worry about having to instantiate the correct instance of that interface.&nbsp; You haven&#39;t indicated anything about who is actually going to be creating all the objects you will be needing.&nbsp; I&#39;m a big fan of the rule that code should either use an object or create it, but not both.&nbsp; That doesn&#39;t necessarily have anything to do with iBatis, but Spring&#39;s DI certainly makes that easier.<br>

<br>Once again, if Spring doesn&#39;t solve any of your problems, don&#39;t use it.&nbsp; But your reasons for not using it seem a little inconsistent.&nbsp; You state that the only thing that Spring would do for you is allow you to use a Spring utility class.&nbsp; But you then state that you don&#39;t want to use DI because you don&#39;t want clients of your API to depend on Spring.&nbsp; Well, those things really are independent of each other.&nbsp; I have nothing to gain by you using Spring, but you might want to take another look at what Spring really does before you decide you don&#39;t want to use it.<br>

</blockquote></div><br>

------=_Part_13461_29338387.1231800139091--