<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: A single POJO persistence model to replace JDO and take over much of EJB??</title>
	<atom:link href="http://technology.amis.nl/2004/10/05/a-single-pojo-persistence-model-to-replace-jdo-and-take-over-much-of-ejb/feed/" rel="self" type="application/rss+xml" />
	<link>http://technology.amis.nl/2004/10/05/a-single-pojo-persistence-model-to-replace-jdo-and-take-over-much-of-ejb/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=a-single-pojo-persistence-model-to-replace-jdo-and-take-over-much-of-ejb</link>
	<description></description>
	<lastBuildDate>Fri, 12 Apr 2013 10:04:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Lucas</title>
		<link>http://technology.amis.nl/2004/10/05/a-single-pojo-persistence-model-to-replace-jdo-and-take-over-much-of-ejb/#comment-932</link>
		<dc:creator>Lucas</dc:creator>
		<pubDate>Fri, 11 Mar 2005 08:46:32 +0000</pubDate>
		<guid isPermaLink="false">/?p=192#comment-932</guid>
		<description><![CDATA[Very interesting interview on The Server Side with Mike Keith and Doug Clarke from the Oracle Toplink team: &lt;a href=&quot;http://www.theserverside.com/news/thread.tss?thread_id=30017&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;TopLink: 10 Years of Persistence.&lt;/a&gt;. It talks about EJB 3.0 and why Oracle left the JDO group. Also what differentiates Toplink from Hibernate and SolarMetric. &lt;blockquote&gt;Mike: TopLink brings with it a strong history and long track record in this market. It is proven, scalable technology that has its feature set evolved from use by thousands of customers building challenging, diverse applications. After 10 years, we have the richest, most powerful feature set available and can address very sophisticated requirements.

Another major differentiating factor is we offer functionality beyond a pure O/R mapping product. We provide the ability to map to XML and other types of non-relational data. TopLink brings much more to the table in terms of the complete data integration story than it ever has before. It is very exciting actually, because as we offer bigger and better solutions it also keeps it interesting for us at the development level. TopLink has proven itself as a leading and visionary product and has lead the way in O/R mapping for a decade, now. We will continue to show leadership as the problem space expands.&lt;/blockquote&gt;]]></description>
		<content:encoded><![CDATA[<p>Very interesting interview on The Server Side with Mike Keith and Doug Clarke from the Oracle Toplink team: <a href="http://www.theserverside.com/news/thread.tss?thread_id=30017" target="_blank" rel="nofollow">TopLink: 10 Years of Persistence.</a>. It talks about EJB 3.0 and why Oracle left the JDO group. Also what differentiates Toplink from Hibernate and SolarMetric.<br />
<blockquote>Mike: TopLink brings with it a strong history and long track record in this market. It is proven, scalable technology that has its feature set evolved from use by thousands of customers building challenging, diverse applications. After 10 years, we have the richest, most powerful feature set available and can address very sophisticated requirements.</p>
<p>Another major differentiating factor is we offer functionality beyond a pure O/R mapping product. We provide the ability to map to XML and other types of non-relational data. TopLink brings much more to the table in terms of the complete data integration story than it ever has before. It is very exciting actually, because as we offer bigger and better solutions it also keeps it interesting for us at the development level. TopLink has proven itself as a leading and visionary product and has lead the way in O/R mapping for a decade, now. We will continue to show leadership as the problem space expands.</p></blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>By: Abe White</title>
		<link>http://technology.amis.nl/2004/10/05/a-single-pojo-persistence-model-to-replace-jdo-and-take-over-much-of-ejb/#comment-931</link>
		<dc:creator>Abe White</dc:creator>
		<pubDate>Wed, 06 Oct 2004 18:20:41 +0000</pubDate>
		<guid isPermaLink="false">/?p=192#comment-931</guid>
		<description><![CDATA[I am a JDO vendor on both the JDO 2 and JSR 220 expert groups.  I&#039;m excited about the opportunity to create a common persistence API for Java, but I have to disagree with you that JDO is a dead end.  JSR 220 is due to ship with J2EE 1.5 in 2006, while JDO 2 will be out in a few months.  JDO 2 is an extremely full-featured spec with excellent ORM.  Most JDO vendors will continue to support JDO 2 for the foreseeable future, since it already contains as least as much functionality as is slated for the eventual JSR 220 spec.  Who knows; JDO might even advance after JDO 2 as a superset of JSR 220!

And even if I cannot convince you that JDO is not a dead end, it is still a standard today.  That means that you can freely switch between the multiple vendors out there, and take advantage of the vendor that comes out with the best migration tools to switch to the new API once J2EE 1.5 is released in 12-15 months.  So even if you believe JDO is a dead-end spec, it still has advantages over using a product that doesn&#039;t adhere to any spec at all.]]></description>
		<content:encoded><![CDATA[<p>I am a JDO vendor on both the JDO 2 and JSR 220 expert groups.  I&#8217;m excited about the opportunity to create a common persistence API for Java, but I have to disagree with you that JDO is a dead end.  JSR 220 is due to ship with J2EE 1.5 in 2006, while JDO 2 will be out in a few months.  JDO 2 is an extremely full-featured spec with excellent ORM.  Most JDO vendors will continue to support JDO 2 for the foreseeable future, since it already contains as least as much functionality as is slated for the eventual JSR 220 spec.  Who knows; JDO might even advance after JDO 2 as a superset of JSR 220!</p>
<p>And even if I cannot convince you that JDO is not a dead end, it is still a standard today.  That means that you can freely switch between the multiple vendors out there, and take advantage of the vendor that comes out with the best migration tools to switch to the new API once J2EE 1.5 is released in 12-15 months.  So even if you believe JDO is a dead-end spec, it still has advantages over using a product that doesn&#8217;t adhere to any spec at all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zeger Hendrikse</title>
		<link>http://technology.amis.nl/2004/10/05/a-single-pojo-persistence-model-to-replace-jdo-and-take-over-much-of-ejb/#comment-930</link>
		<dc:creator>Zeger Hendrikse</dc:creator>
		<pubDate>Wed, 06 Oct 2004 07:26:41 +0000</pubDate>
		<guid isPermaLink="false">/?p=192#comment-930</guid>
		<description><![CDATA[After reading this post, I got a much better idea on the current situation of the &quot;ORM market&quot;. Great!]]></description>
		<content:encoded><![CDATA[<p>After reading this post, I got a much better idea on the current situation of the &#8220;ORM market&#8221;. Great!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
