Mailing-List: contact jdo-commits-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
From: jdo-commits@db.apache.org
To: jdo-commits@db.apache.org
Subject: =?iso-8859-1?q?=5BApache_JDO_Wiki=5D_Updated=3A__FrontPage?=
Date: Sat, 08 Jan 2005 01:31:43 -0000
Message-ID: <20050108013143.8399.39101@minotaur.apache.org>

   Date: 2005-01-07T17:31:43
   Editor: CraigRussell
   Wiki: Apache JDO Wiki
   Page: FrontPage
   URL: http://wiki.apache.org/jdo/FrontPage

   no comment

Change Log:

---------------------------------------------------------------------------=
---
@@ -17,9 +17,9 @@
 =

  * JDO 1.0 API. This is the standard definition of the JDO API as defined =
by the JSR-12 standard.
 =

- * JDO 1.0 Reference Implementation. This is a file-based, single-user sto=
re for persistent Java objects.
+ * JDO 1.1 Reference Implementation. This is a file-based, single-user sto=
re for persistent Java objects. The version number is 1.1 to reflect that t=
he Java package has changed from com.sun.jdori to org.apache.jdo.
 =

- * JDO 1.0 Technology Compatibility Kit. This set of programs tests that a=
 JDO 1.0 implementation is in compliance with the standard.
+ * JDO 1.1 Technology Compatibility Kit. This set of programs tests that a=
 JDO 1.0 implementation is in compliance with the standard. The version num=
ber is 1.1 to reflect that the test framework has changed from [http://java=
.sun.com/developer/technicalArticles/JCPtools2/ JavaTest] (a proprietary Su=
n package not suitable for open source projects) to[http://www.junit.org/in=
dex.htm JUnit], an open source test framework.
 =

  * JDO 2.0 API. This is the standard definition of the JDO API as defined =
by the JSR-243 standard.
 =

@@ -27,7 +27,7 @@
 =

  * JDO 2.0 FOStore (File Object Store) implementation. This is an implemen=
tation of JDO 2.0 based on the JDO 1.0 Reference Implementation. It does no=
t support relational data access, so it is inappropriate for the JDO 2.0 Re=
ference Implementation. See below.
 =

- * JDO 2.0 Geronimo Integration. This project will build the glue between =
the JDO 2.0 Reference Implementation and the J2EE compliant application ser=
ver. We expect to use a common persistence framework to provide both EJB3 a=
nd JDO persistence services.
+ * JDO 2.0 Geronimo Integration. This project will build the glue between =
the JDO 2.0 Reference Implementation and the J2EE compliant application ser=
ver. We expect to use a common persistence framework (Tranql) to provide bo=
th EJB3 and JDO persistence services.
 =

 Due to timing constraints, the JDO 2.0 Reference Implementation is not bei=
ng built as an Apache project, but will be built as a JPOX release http://j=
pox.org.
 =

@@ -49,11 +49,13 @@
 =

 Information for developers of the JDO TCK is found at TechnologyCompatibil=
ityKitDevelopers
 =

-=3D Developer Information =3D
+=3D General Developer Information =3D
 =

-JDO will use the same coding standards as the Geronimo project: ApacheGero=
nimo:CodingStandards.
+ * JDO will use the same coding standards as the Geronimo project: ApacheG=
eronimo:CodingStandards.
 =

-There are a number of items on the ToDoList. You can volunteer for any of =
them...
+ * There are a number of items on the ToDoList. You can volunteer for any =
of them...
+
+ * The subversion repository is being set up. You can take a look at the S=
ubversionRepository page for more information.
 =

 =3D Downloads =3D
=20