<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Using Hibernate Synchronizer 3.1.9 with Spring and Hibernate 3</title>
	<link>http://www.supergloo.com/blog/index.php/2006/11/16/using-hibernate-synchronizer-319-with-spring-and-hibernate-3/</link>
	<description>Outsource Web Development</description>
	<pubDate>Sat, 19 May 2012 09:04:57 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0</generator>

	<item>
		<title>by: dPedro</title>
		<link>http://www.supergloo.com/blog/index.php/2006/11/16/using-hibernate-synchronizer-319-with-spring-and-hibernate-3/#comment-348</link>
		<pubDate>Mon, 18 Dec 2006 09:03:56 +0000</pubDate>
		<guid>http://www.supergloo.com/blog/index.php/2006/11/16/using-hibernate-synchronizer-319-with-spring-and-hibernate-3/#comment-348</guid>
					<description>Again about the interfaces. One of the top Spring guideline is easy testing eith dependency injection. I think it's enough to use them.

Personally I use interfaces to mock my daos while unit testing business logic layer.

Good article, good work :)</description>
		<content:encoded><![CDATA[<p>Again about the interfaces. One of the top Spring guideline is easy testing eith dependency injection. I think it&#8217;s enough to use them.</p>
<p>Personally I use interfaces to mock my daos while unit testing business logic layer.</p>
<p>Good article, good work <img src='http://www.supergloo.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Rubbin</title>
		<link>http://www.supergloo.com/blog/index.php/2006/11/16/using-hibernate-synchronizer-319-with-spring-and-hibernate-3/#comment-324</link>
		<pubDate>Mon, 11 Dec 2006 06:40:23 +0000</pubDate>
		<guid>http://www.supergloo.com/blog/index.php/2006/11/16/using-hibernate-synchronizer-319-with-spring-and-hibernate-3/#comment-324</guid>
					<description>Hi, glad to read your artical.But I have a question that how to generate the spring config file automatically.It seems no mention about it.Just edit by hand?Will you please help me?</description>
		<content:encoded><![CDATA[<p>Hi, glad to read your artical.But I have a question that how to generate the spring config file automatically.It seems no mention about it.Just edit by hand?Will you please help me?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Rob Ottaway</title>
		<link>http://www.supergloo.com/blog/index.php/2006/11/16/using-hibernate-synchronizer-319-with-spring-and-hibernate-3/#comment-305</link>
		<pubDate>Sun, 03 Dec 2006 18:27:40 +0000</pubDate>
		<guid>http://www.supergloo.com/blog/index.php/2006/11/16/using-hibernate-synchronizer-319-with-spring-and-hibernate-3/#comment-305</guid>
					<description>Thanks for writing such a helpful article! I think it is a very good start for getting people going with Spring/HibernateSynchronizer. I have to point out though that deleting the interfaces is a mistake :)

If you use the interfaces it will be much easier to switch out the form of backing for your DAO. You may be in the mind set that you only use hibernate/database behind the DAO. But what if you need to change your DAO implementation being used? What if the CIO of your company demands it? Maybe it will be backed by a SOAP service or messaging system? If you only have a concrete class. The class will be strongly coupled into all the code you wrote that used the DAO class.

With Spring it is especially easy to switch out one DAO implementation with another (if you use interfaces!). I'm guessing you don't really have much need for reusing the database code generated by Synchronizer?

Just my 2 cents. Thanks for the good article.</description>
		<content:encoded><![CDATA[<p>Thanks for writing such a helpful article! I think it is a very good start for getting people going with Spring/HibernateSynchronizer. I have to point out though that deleting the interfaces is a mistake <img src='http://www.supergloo.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>If you use the interfaces it will be much easier to switch out the form of backing for your DAO. You may be in the mind set that you only use hibernate/database behind the DAO. But what if you need to change your DAO implementation being used? What if the CIO of your company demands it? Maybe it will be backed by a SOAP service or messaging system? If you only have a concrete class. The class will be strongly coupled into all the code you wrote that used the DAO class.</p>
<p>With Spring it is especially easy to switch out one DAO implementation with another (if you use interfaces!). I&#8217;m guessing you don&#8217;t really have much need for reusing the database code generated by Synchronizer?</p>
<p>Just my 2 cents. Thanks for the good article.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Domenico</title>
		<link>http://www.supergloo.com/blog/index.php/2006/11/16/using-hibernate-synchronizer-319-with-spring-and-hibernate-3/#comment-294</link>
		<pubDate>Sat, 25 Nov 2006 18:02:02 +0000</pubDate>
		<guid>http://www.supergloo.com/blog/index.php/2006/11/16/using-hibernate-synchronizer-319-with-spring-and-hibernate-3/#comment-294</guid>
					<description>Hi, I not found che Class Constructors of any DAO, can you help me?</description>
		<content:encoded><![CDATA[<p>Hi, I not found che Class Constructors of any DAO, can you help me?
</p>
]]></content:encoded>
				</item>
</channel>
</rss>

