<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Just A Quick Note on Frameworks</title>
	<atom:link href="http://blog.james-carr.org/2007/10/03/just-a-quick-note-on-frameworks/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.james-carr.org/2007/10/03/just-a-quick-note-on-frameworks/</link>
	<description>Rants and Musings of an Agile Developer</description>
	<pubDate>Sat, 22 Nov 2008 04:59:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Than Som</title>
		<link>http://blog.james-carr.org/2007/10/03/just-a-quick-note-on-frameworks/#comment-41055</link>
		<dc:creator>Than Som</dc:creator>
		<pubDate>Thu, 06 Dec 2007 21:30:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.james-carr.org/2007/10/03/just-a-quick-note-on-frameworks/#comment-41055</guid>
		<description>James is Crazy!!!!!!!!!!!!!! Blogger.</description>
		<content:encoded><![CDATA[<p>James is Crazy!!!!!!!!!!!!!! Blogger.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Sage</title>
		<link>http://blog.james-carr.org/2007/10/03/just-a-quick-note-on-frameworks/#comment-40253</link>
		<dc:creator>Chris Sage</dc:creator>
		<pubDate>Wed, 28 Nov 2007 15:18:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.james-carr.org/2007/10/03/just-a-quick-note-on-frameworks/#comment-40253</guid>
		<description>I know you already know this, but you can tell them:

It does a few things:

* Solution with the least amount of effort (complex models from simple components)
* Easy easy dependency injection! Yay!
* AOP - makes crosscutting concerns nice and easy, in example  with interceptors for logging or security
* Spring support for Persistence Frameworks.  Man, oh man, does this make me happy since it will plug into Ibatis, Hibernate, JDO, Java Persistence API and supports all those languages with their DAO support modules.  No longer do I have to write a bunch of extra support code - and it will close the connections and all that for you!  You guys would be able to say goodbye to Kurt's Hibernate manager thing. :) 
* Those DataSources can be changed with just loading a different file into the context, whether it be getting the datasource from the JDNI, Hibernate Transaction Manager or whatever, it's all transparent.
*It can also be used instead of Struts for the MVC</description>
		<content:encoded><![CDATA[<p>I know you already know this, but you can tell them:</p>
<p>It does a few things:</p>
<p>* Solution with the least amount of effort (complex models from simple components)<br />
* Easy easy dependency injection! Yay!<br />
* AOP - makes crosscutting concerns nice and easy, in example  with interceptors for logging or security<br />
* Spring support for Persistence Frameworks.  Man, oh man, does this make me happy since it will plug into Ibatis, Hibernate, JDO, Java Persistence API and supports all those languages with their DAO support modules.  No longer do I have to write a bunch of extra support code - and it will close the connections and all that for you!  You guys would be able to say goodbye to Kurt&#8217;s Hibernate manager thing. <img src='http://blog.james-carr.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /><br />
* Those DataSources can be changed with just loading a different file into the context, whether it be getting the datasource from the JDNI, Hibernate Transaction Manager or whatever, it&#8217;s all transparent.<br />
*It can also be used instead of Struts for the MVC</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik Weibust</title>
		<link>http://blog.james-carr.org/2007/10/03/just-a-quick-note-on-frameworks/#comment-33410</link>
		<dc:creator>Erik Weibust</dc:creator>
		<pubDate>Thu, 04 Oct 2007 13:38:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.james-carr.org/2007/10/03/just-a-quick-note-on-frameworks/#comment-33410</guid>
		<description>Great point.  Businesses need a lot of money to throw at a project to afford the time to come up with a better solution then what Spring, Hibernate, and other frameworks provide.  Yes, they could then use the homegrown DI or ORM solution in future projects at the company, but they would still have to support/enhance the framework which would cost money.

I normally recommend free/open source projects with the logic that if it's a good project, with interest, it will only continue to get better being open.  Over time there will be more people testing/debugging/improving an open source framework  then what a company could do "in house". 

Erik</description>
		<content:encoded><![CDATA[<p>Great point.  Businesses need a lot of money to throw at a project to afford the time to come up with a better solution then what Spring, Hibernate, and other frameworks provide.  Yes, they could then use the homegrown DI or ORM solution in future projects at the company, but they would still have to support/enhance the framework which would cost money.</p>
<p>I normally recommend free/open source projects with the logic that if it&#8217;s a good project, with interest, it will only continue to get better being open.  Over time there will be more people testing/debugging/improving an open source framework  then what a company could do &#8220;in house&#8221;. </p>
<p>Erik</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick</title>
		<link>http://blog.james-carr.org/2007/10/03/just-a-quick-note-on-frameworks/#comment-33409</link>
		<dc:creator>Rick</dc:creator>
		<pubDate>Thu, 04 Oct 2007 13:09:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.james-carr.org/2007/10/03/just-a-quick-note-on-frameworks/#comment-33409</guid>
		<description>I agree completely.

While it is probably true that "Any programmer worth their salt would be able to write a simple event handling mechanism.", do you really want to be the programmer who has to write that mechanism again and again and again and again as he/she moves from team to team and firm to firm? Writing it once may well be fun and instructive, but it gets old fast.

I sure don't. Spring (and like frameworks) take away the gumpf and alow you to concentrate on the the important (and unique) bit, namely the domain.</description>
		<content:encoded><![CDATA[<p>I agree completely.</p>
<p>While it is probably true that &#8220;Any programmer worth their salt would be able to write a simple event handling mechanism.&#8221;, do you really want to be the programmer who has to write that mechanism again and again and again and again as he/she moves from team to team and firm to firm? Writing it once may well be fun and instructive, but it gets old fast.</p>
<p>I sure don&#8217;t. Spring (and like frameworks) take away the gumpf and alow you to concentrate on the the important (and unique) bit, namely the domain.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
