<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://merrickschincariol.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Merrick Schincariol</title>
 <link>http://merrickschincariol.sys-con.com/</link>
 <description>Latest News from Merrick Schincariol</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Wed, 09 Dec 2009 03:08:03 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>Portable Persistence Using the EJB 3.0 Java Persistence API</title>
 <link>http://merrickschincariol.sys-con.com/node/286874</link>
 <description>Experience has taught us that it&#039;s not enough to simply have a persistence standard as part of an enterprise specification. It must be a standard that can solve people&#039;s problems and be useful to most of the  applications that want to use it. While earlier versions of Enterprise JavaBeans (EJB) persistence met some of the needs, they were primarily focused on the distributed problem domain. It is now known, and has been proven by successful commercial products like Oracle TopLink and Open Source projects like JBoss Hibernate, that the objects to be persisted don&#039;t have to be anything more than simple Java objects. The proof was in the popularity of these Object-Relational Mapping (ORM) tools; most developers have tended to pick up and use these tools rather than adopt the Java 2 Enterprise Edition (J2EE) entity bean programming standard.&lt;p&gt;&lt;a href=&quot;http://merrickschincariol.sys-con.com/node/286874&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 20 Oct 2006 14:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://merrickschincariol.sys-con.com/node/286874</guid>
 <comments>http://merrickschincariol.sys-con.com/node/286874#feedback</comments>
</item>
</channel>
</rss>
