<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://mikekeith.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Mike Keith</title>
 <link>http://mikekeith.sys-con.com/</link>
 <description>Latest News from Mike Keith</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Wed, 09 Dec 2009 04:32:48 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>Java Feature — Using the Java Persistence API (JPA) with Spring 2.0</title>
 <link>http://mikekeith.sys-con.com/node/366275</link>
 <description>The EJB 3.0 Java Persistence API (JPA) was released in May 2006 as part of the Java Enterprise Edition 5 (Java EE) platform, and it has already garnered a great deal of attention and praise. What began as merely an easier-to-use successor to the much-maligned container-managed persistence (CMP) portion of the EJB component standard soon evolved into a full-blown incorporation of the existing best practices of the most prominent and popular object-relational (O-R) persistence products in use. The result is that applications now have a modern standard for lightweight enterprise Java persistence that they can use in any compliant Java EE 5 application server, or in Java Standard Edition (SE) applications.&lt;p&gt;&lt;a href=&quot;http://mikekeith.sys-con.com/node/366275&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 30 Apr 2007 14:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://mikekeith.sys-con.com/node/366275</guid>
 <comments>http://mikekeith.sys-con.com/node/366275#feedback</comments>
</item>
<item>
 <title>Portable Persistence Using the EJB 3.0 Java Persistence API</title>
 <link>http://mikekeith.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://mikekeith.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://mikekeith.sys-con.com/node/286874</guid>
 <comments>http://mikekeith.sys-con.com/node/286874#feedback</comments>
</item>
</channel>
</rss>
