db-jdo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From an...@apache.org
Subject svn commit: r586702 - in /db/jdo/site: docs/why_jdo.html xdocs/why_jdo.xml
Date Sat, 20 Oct 2007 10:59:53 GMT
Author: andyj
Date: Sat Oct 20 03:59:52 2007
New Revision: 586702

URL: http://svn.apache.org/viewvc?rev=586702&view=rev
Log:
JDO-539 JPA wording

Modified:
    db/jdo/site/docs/why_jdo.html
    db/jdo/site/xdocs/why_jdo.xml

Modified: db/jdo/site/docs/why_jdo.html
URL: http://svn.apache.org/viewvc/db/jdo/site/docs/why_jdo.html?rev=586702&r1=586701&r2=586702&view=diff
==============================================================================
--- db/jdo/site/docs/why_jdo.html (original)
+++ db/jdo/site/docs/why_jdo.html Sat Oct 20 03:59:52 2007
@@ -15,7 +15,7 @@
                     principle, being designed with flexibility and datastore agnositicity
in mind.
                     This has been a standard since 2002 (JDO1), being upgraded in 2006 (JDO2)
and
                     is in the process of being developed further (JDO2.1) by Apache JDO</li>
-                <li>You can use <B>JPA1</B>, a standardised persistence
API, and part of the EJB3 specification. This also allows you to
+                <li>You can use <B>JPA</B>, a standardised persistence
API, and part of the EJB3 specification. This also allows you to
                     to develop plain old Java objects (POJOs) and persist them using a standardised
API. It's specification
                     is not as mature or as feature rich as the JDO API, nor does it provide
the flexibility
                     of using any type of datastore. This was released in 2006 (JPA1) to supercede
EJB2</li>

Modified: db/jdo/site/xdocs/why_jdo.xml
URL: http://svn.apache.org/viewvc/db/jdo/site/xdocs/why_jdo.xml?rev=586702&r1=586701&r2=586702&view=diff
==============================================================================
--- db/jdo/site/xdocs/why_jdo.xml (original)
+++ db/jdo/site/xdocs/why_jdo.xml Sat Oct 20 03:59:52 2007
@@ -21,7 +21,7 @@
                     principle, being designed with flexibility and datastore agnositicity
in mind.
                     This has been a standard since 2002 (JDO1), being upgraded in 2006 (JDO2)
and
                     is in the process of being developed further (JDO2.1) by Apache JDO</li>
-                <li>You can use <B>JPA1</B>, a standardised persistence
API, and part of the EJB3 specification. This also allows you to
+                <li>You can use <B>JPA</B>, a standardised persistence
API, and part of the EJB3 specification. This also allows you to
                     to develop plain old Java objects (POJOs) and persist them using a standardised
API. It's specification
                     is not as mature or as feature rich as the JDO API, nor does it provide
the flexibility
                     of using any type of datastore. This was released in 2006 (JPA1) to supercede
EJB2</li>



Mime
View raw message