<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>

<channel>
	<title>aco</title>
	<link>http://blogs.exist.com/aco</link>
	<description>Anything Cool in Open source...</description>
	<pubDate>Fri, 28 Mar 2008 10:23:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
	<language>en</language>
			<item>
		<title>Specifying Different Databases for Unit and System Testing</title>
		<link>http://blogs.exist.com/aco/2008/03/28/specifying-different-databases-for-unit-and-system-testing/</link>
		<comments>http://blogs.exist.com/aco/2008/03/28/specifying-different-databases-for-unit-and-system-testing/#comments</comments>
		<pubDate>Fri, 28 Mar 2008 10:23:06 +0000</pubDate>
		<dc:creator>Adrian Co</dc:creator>
		
		<category><![CDATA[Java]]></category>

		<category><![CDATA[ORM]]></category>

		<category><![CDATA[Testing]]></category>

		<category><![CDATA[jpa]]></category>

		<category><![CDATA[maven]]></category>

		<category><![CDATA[spring]]></category>

		<category><![CDATA[unit test]]></category>

		<guid isPermaLink="false">http://blogs.exist.com/aco/2008/03/28/specifying-different-databases-for-unit-and-system-testing/</guid>
		<description><![CDATA[Quality software requires thorough testing. Most applications today also utilize databases for persistent storage. As such, being able to test your application against your target database is important, be it unit testing, functional testing, or system testing.
One of the key points in unit testing code that performs database operations is that the database must always [...]]]></description>
		<wfw:commentRss>http://blogs.exist.com/aco/2008/03/28/specifying-different-databases-for-unit-and-system-testing/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Reusing JPA models using embedded entities and composition</title>
		<link>http://blogs.exist.com/aco/2008/03/24/reusing-jpa-models-using-embedded-entities-and-composition/</link>
		<comments>http://blogs.exist.com/aco/2008/03/24/reusing-jpa-models-using-embedded-entities-and-composition/#comments</comments>
		<pubDate>Mon, 24 Mar 2008 10:28:58 +0000</pubDate>
		<dc:creator>Adrian Co</dc:creator>
		
		<category><![CDATA[Java]]></category>

		<category><![CDATA[ORM]]></category>

		<category><![CDATA[design]]></category>

		<category><![CDATA[embeddable]]></category>

		<category><![CDATA[embedded]]></category>

		<category><![CDATA[entitylisteners]]></category>

		<category><![CDATA[jpa]]></category>

		<category><![CDATA[openjpa]]></category>

		<category><![CDATA[persistence]]></category>

		<category><![CDATA[prepersist]]></category>

		<category><![CDATA[preupdate]]></category>

		<guid isPermaLink="false">http://blogs.exist.com/aco/2008/03/24/reusing-jpa-models-using-embedded-entities-and-composition/</guid>
		<description><![CDATA[We&#8217;ve all heard of the debate regarding inheritance vs composition. Composition is certainly favored more over inheritance unless there is an &#8220;is-a&#8221; relationship between two classes.
In the ORM world, specifically in JPA, composition is achieved using join-relationships (i.e. One-To-One, One-To-Many, Many-To-One, Many-To-Many), often overlooked is the functionality to embed a class in your models using [...]]]></description>
		<wfw:commentRss>http://blogs.exist.com/aco/2008/03/24/reusing-jpa-models-using-embedded-entities-and-composition/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
