db-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From an...@apache.org
Subject svn commit: r892842 [15/15] - in /websites/production/db/content/jdo: ./ guides/ releases/
Date Sun, 05 Jan 2014 10:08:46 GMT
Modified: websites/production/db/content/jdo/svn.html
==============================================================================
--- websites/production/db/content/jdo/svn.html (original)
+++ websites/production/db/content/jdo/svn.html Sun Jan  5 10:08:45 2014
@@ -1,5 +1,5 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia Site Renderer 1.3 at Nov 4, 2013 -->
+<!-- Generated by Apache Maven Doxia Site Renderer 1.3 at Jan 5, 2014 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
   <head>
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
@@ -12,7 +12,7 @@
     </style>
     <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
       <meta name="author" content="JDO Documentation Team" />
-    <meta name="Date-Revision-yyyymmdd" content="20131104" />
+    <meta name="Date-Revision-yyyymmdd" content="20140105" />
     <meta http-equiv="Content-Language" content="en" />
         
         </head>
@@ -102,7 +102,7 @@
                   <li class="none">
                           <a href="field_types.html" title="Types of Fields">Types of Fields</a>
             </li>
-                                                                                                                          <li class="collapsed">
+                                                                                                                                            <li class="collapsed">
                           <a href="metadata.html" title="MetaData">MetaData</a>
                   </li>
                   <li class="none">
@@ -210,179 +210,179 @@
     </div>
     <div id="bodyColumn">
       <div id="contentBox">
-        <!-- Licensed to the Apache Software Foundation (ASF) under one or more
-contributor license agreements.  See the NOTICE file distributed with
-this work for additional information regarding copyright ownership.
-The ASF licenses this file to You under the Apache License, Version 2.0
-(the "License"); you may not use this file except in compliance with
-the License.  You may obtain a copy of the License at
-
-    http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software 
-distributed under the License is distributed on an "AS IS" BASIS, 
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 
-See the License for the specific language governing permissions and 
-limitations under the License. -->
-
- 
-
-<div class="section"><h2>Source Code Version Control<a name="Source_Code_Version_Control"></a></h2>
-
-<p>Apache JDO uses <a class="external" href="http://subversion.tigris.org" rel="nofollow">Subversion</a> to manage its source code.
-If you're new to Subversion, you can check out the
-<a class="externalLink" href="http://svnbook.red-bean.com/">online book</a> about Subversion.
-Note that we are currently using Subversion 1.1.x (there are separate
-versions of the book covering 1.0 and 1.1).
-</p>
-<p>
-To receive notice of commits to the repository subscribe to <a class="externalLink" href="mailto:jdo-commits@db.apache.org">jdo-commits@db.apache.org</a> by sending email to <a class="externalLink" href="mailto:jdo-commits-subscribe@db.apache.org">jdo-commits-subscribe@db.apache.org</a>. </p>
-
-</div>
-
-<div class="section"><h2>Web Access to Subversion<a name="Web_Access_to_Subversion"></a></h2>
-
-<p>
-If you just want to browse the source code, you can use the
-<a class="external" href="http://svn.apache.org/viewcvs/db/jdo" rel="nofollow">
-ViewCVS web interface</a> to Subversion.  This is current at all times.
-</p>
-
-</div>
-
-<div class="section"><h2>Checking Out Code Using Subversion<a name="Checking_Out_Code_Using_Subversion"></a></h2>
-
-<p>Anyone can check code out of Subversion.  You only need to specify a
-username and password to update the Subversion repository, and only
-JDO committers can do that.
-If you are a committer, are working from behind a firewall, or are connected to the internet through a proxy server, please see the sections below for more information.</p>
-
-<div class="section"><h3>Anonymous check out from Subversion<a name="Anonymous_check_out_from_Subversion"></a></h3>
-<p>Use a command like:</p>
-<div><pre>% svn checkout http://svn.apache.org/repos/asf/db/jdo </pre></div>
-<p>Once you have Apache JDO checked out you can update the source by executing the following command from within the jdo. </p>
-<div><pre>
-% svn update
-</pre></div>
-</div>
-<div class="section"><h3>Access from behind a firewall<a name="Access_from_behind_a_firewall"></a></h3>
-
-<p>For those users who are stuck behind a corporate firewall which is blocking http access to the Subversion repository, you can try to access it via HTTPS: </p>
-<div><pre>
-% svn checkout https://svn.apache.org/repos/asf/db/jdo
-</pre></div>
-
-</div>
-<div class="section"><h3>Access through a proxy<a name="Access_through_a_proxy"></a></h3>
-
-<p>The Subversion client can go through a proxy, if you configure it to do so. First, edit your &quot;servers&quot; configuration file to indicate which proxy to use. The files location depends on your operating system. On Linux or Unix it is located in the directory &quot;~/.subversion&quot;. On Windows it is in &quot;%APPDATA%\Subversion&quot;. (Try &quot;echo %APPDATA%&quot;, note this is a hidden directory.) </p>
-<p>There are comments in the file explaining what to do. If you don't have that file, get the latest Subversion client and run any command; this will cause the configuration directory and template files to be created. </p>
-<p>Example : Edit the 'servers' file and add something like : </p>
-<div><pre>
-[global]
-http-proxy-host = your.proxy.name
-http-proxy-port = 3128
-</pre></div>
-<p>Please use the regular http proxy settings in case you want to access the the repository from the Sun network (SWAN). </p>
-
-</div>
-
-<div class="section"><h3>Committer access<a name="Committer_access"></a></h3>
-
-<p>Everyone can access the Apache JDO Subversion repository via HTTPS, but Apache JDO Committers must checkout the Subversion repository via HTTPS. </p>
-<div><pre>
-% svn checkout https://svn.apache.org/repos/asf/db/jdo
-</pre></div>
-</div>
-<div class="section"><h3>NetBeans CVS repository access<a name="NetBeans_CVS_repository_access"></a></h3>
-
-<p>The btree subproject checks out the NetBeans mdr btree implementation. This requires cvs being installed on your system. The official NetBeans cvs host might not work if you are behind a firewall that blocks the cvs port. Please consult the <a class="external" href="http://www.netbeans.org/community/sources" rel="nofollow">NetBeans sources</a> page for more info.  </p>
-<p>If you do not have a cvs client installed on your system you can download the NetBeans mdr btree sources <a href="/jdo-data/attachments/SubversionRepository/attachments/netbeans-mdr-btree.zip">here</a>. Unzip the file in the btree directory and comment out (or remove) the definition of the preGoal java:prepare-filesystem. </p>
-</div>
-</div>
-
-<div class="section"><h2>Submitting Code Changes<a name="Submitting_Code_Changes"></a></h2>
-<div class="section"><h3>Submitting a patch<a name="Submitting_a_patch"></a></h3>
-
-<p>If you make changes to Apache JDO, and would like to contribute the to the project, you should create a patch and send it to the jdo-dev alias <a class="externalLink" href="mailto:jdo-dev@db.apache.org">jdo-dev@db.apache.org</a>.  To create a patch, simply execute the following command: </p>
-<div><pre>
-% svn diff &gt; your-changes.patch
-</pre></div>
-</div>
-
-<div class="section"><h3>Committing changes to subversion<a name="Committing_changes_to_subversion"></a></h3>
-<p>
-To commit changes to the Subversion repository, you must be an Apache JDO committer.  See <a href="get-involved.html">Get Involved</a> for information on how to become a committer and how to set up your password once you become a committer.
-</p>
-
-<p>
-Once your password is set, you can use a command like this to commit:
-</p>
-<div><pre>
-$&gt; svn commit --username your-username
-Authentication realm: &lt;https://svn.apache.org:443&gt; ASF Committers
-Password for 'your-username': your-password
-</pre></div>
-<p>You can also pass your password on the command line directly, but this is a security problem on multiuser unix computers (the command line arguments are available via the ps command).  Here is the command if you are Windows or a single user unix computer: </p>
-<div><pre>
-$&gt; svn commit --username your-username --password your-password
-</pre></div>
-<p>Remember to replace 'your-username' and 'your-password' with your actual username and password on svn.apache.org. </p>
-
-</div>
-</div>
-
-<div class="section"><h2>Building JDO from Source<a name="Building_JDO_from_Source"></a></h2>
-<p>Refer to the <a class="externalLink" href="http://wiki.apache.org/jdo/FrontPage">Wiki
-page</a> for details. Note that the JDO project is subdivided into several
-smaller projects, and each project is built separately. </p>
-
-</div>
-
-<div class="section"><h2>Using Subversion on Windows with cygwin<a name="Using_Subversion_on_Windows_with_cygwin"></a></h2>
-
-<p>If you use Subversion on Windows under cygwin, you may find that the Subversion client automatically assigns the executable property to non-executable files. In that case, you would see this at the bottom of an <i>svn diff</i> of the file: 
-</p>
-<div><pre>
-Property changes on: test/sql/derby/datastoreidentity/schema1.sql
-___________________________________________________________________
-Name: svn:executable
-   + *
-</pre></div>
-<p>This section explains the source of the problem and suggests some actions to avoid it. </p>
-
-<div class="section"><h3>Background<a name="Background"></a></h3>
-
-<p>Subversion carries executable information in the built-in property called svn:executable.  This property, unlike others,  may be present or absent, but it has no value.  You can add it or delete it, but but you cannot change its value. </p>
-<p>In theory, Subversion ignores Windows file permissions and by default does not set svn:executable. However, cygwin svn acts like Unix svn and determines the svn:executable property based on file permissions. </p>
-<p>If you create a file from the cygwin command line, by default it is executable only if the filename ends with .bat, .com or .exe, or if its content starts with #!. [This is what the doc says, but you may see -x for all files.] If you create a file using a Windows tool, by default its Windows permissions are executable by all. Cygwin interprets the Unix-style permissions this way as well. If the file is executable by all, cygwin svn sets the svn:executable property on the file when you invoke <i>svn add</i>. </p>
-</div>
-<div class="section"><h3>Removing existing executable properties from the repository<a name="Removing_existing_executable_properties_from_the_repository"></a></h3>
-
-<p>You can use svn propdel to remove the svn:executable property from your working copy. 
-</p>
-<div><pre>
-    svn propdel -R svn:executable .
-</pre></div>
-<p>will recursively remove the svn:executable property from all of the files below the current directory.  You can use this and commit the files to clean the repository if necessary. </p>
-
-</div>
-<div class="section"><h3>Preventing Subversion from adding unwanted executable properties<a name="Preventing_Subversion_from_adding_unwanted_executable_properties"></a></h3>
-
-<p>Windows/cygwin users who don't want to have to think about using <i>svn propdel</i> or <i>chmod</i> on each added file can use a non-cygwin version of svn. The Subversion 1.2.3 Win32 binaries, downloadable from the link at the bottom of <a class="externalLink" href="http://subversion.tigris.org/project_packages.html" rel="nofollow">http://subversion.tigris.org/project_packages.html</a>, appear to work well. After installation add the svn.exe location to your Windows PATH variable. If you are switching from cygwin svn to Win32 svn </p>
-<ol style="list-style-type: decimal">
-<li><p>Remove the subversion component from your cygwin installation because when svn is invoked from a cygwin window, the cygwin version is found even if your cygwin/bin directory is later on the path. (In the Select Packages window of the setup wizard, navigate to the subversion package in the Devel. category.  Click on the status icon until Uninstall is displayed. Click next and continue through the wizard until installation is complete.) </p>
-
-</li>
-<li><p>Copy the servers file and the auth folder from the sygwin ~/.subversion directory to C:\Documents and Settings\&lt;user&gt;\Application Data\Subversion used by Win32 subversion. </p>
-</li>
-</ol>
-<p>Note that windows svn uses backslash as the path separator when displaying file names. You cannot just copy and paste this file name to another svn command when running from within a cygwin shell. You need to enclose the file name into double quotes. </p>
-<p>Alternatively, Windows users can set file permissions in Windows Explorer. (Right-click on the top-level folder &amp; select Properties. Select the Security tab. Click Advanced. Remove all instances of Read &amp; Execute from the Permission Entries. Click &quot;Reset permissions on all child objects and enable propogations of inheritable permissions&quot;. Click Apply. OK. OK.) You will have to do this again when you do a clean checkout to a new directory. </p>
-
-</div>
-</div>
-
+        <!-- Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software 
+distributed under the License is distributed on an "AS IS" BASIS, 
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 
+See the License for the specific language governing permissions and 
+limitations under the License. -->
+
+ 
+
+<div class="section"><h2>Source Code Version Control<a name="Source_Code_Version_Control"></a></h2>
+
+<p>Apache JDO uses <a class="external" href="http://subversion.tigris.org" rel="nofollow">Subversion</a> to manage its source code.
+If you're new to Subversion, you can check out the
+<a class="externalLink" href="http://svnbook.red-bean.com/">online book</a> about Subversion.
+Note that we are currently using Subversion 1.1.x (there are separate
+versions of the book covering 1.0 and 1.1).
+</p>
+<p>
+To receive notice of commits to the repository subscribe to <a class="externalLink" href="mailto:jdo-commits@db.apache.org">jdo-commits@db.apache.org</a> by sending email to <a class="externalLink" href="mailto:jdo-commits-subscribe@db.apache.org">jdo-commits-subscribe@db.apache.org</a>. </p>
+
+</div>
+
+<div class="section"><h2>Web Access to Subversion<a name="Web_Access_to_Subversion"></a></h2>
+
+<p>
+If you just want to browse the source code, you can use the
+<a class="external" href="http://svn.apache.org/viewcvs/db/jdo" rel="nofollow">
+ViewCVS web interface</a> to Subversion.  This is current at all times.
+</p>
+
+</div>
+
+<div class="section"><h2>Checking Out Code Using Subversion<a name="Checking_Out_Code_Using_Subversion"></a></h2>
+
+<p>Anyone can check code out of Subversion.  You only need to specify a
+username and password to update the Subversion repository, and only
+JDO committers can do that.
+If you are a committer, are working from behind a firewall, or are connected to the internet through a proxy server, please see the sections below for more information.</p>
+
+<div class="section"><h3>Anonymous check out from Subversion<a name="Anonymous_check_out_from_Subversion"></a></h3>
+<p>Use a command like:</p>
+<div><pre>% svn checkout http://svn.apache.org/repos/asf/db/jdo </pre></div>
+<p>Once you have Apache JDO checked out you can update the source by executing the following command from within the jdo. </p>
+<div><pre>
+% svn update
+</pre></div>
+</div>
+<div class="section"><h3>Access from behind a firewall<a name="Access_from_behind_a_firewall"></a></h3>
+
+<p>For those users who are stuck behind a corporate firewall which is blocking http access to the Subversion repository, you can try to access it via HTTPS: </p>
+<div><pre>
+% svn checkout https://svn.apache.org/repos/asf/db/jdo
+</pre></div>
+
+</div>
+<div class="section"><h3>Access through a proxy<a name="Access_through_a_proxy"></a></h3>
+
+<p>The Subversion client can go through a proxy, if you configure it to do so. First, edit your &quot;servers&quot; configuration file to indicate which proxy to use. The files location depends on your operating system. On Linux or Unix it is located in the directory &quot;~/.subversion&quot;. On Windows it is in &quot;%APPDATA%\Subversion&quot;. (Try &quot;echo %APPDATA%&quot;, note this is a hidden directory.) </p>
+<p>There are comments in the file explaining what to do. If you don't have that file, get the latest Subversion client and run any command; this will cause the configuration directory and template files to be created. </p>
+<p>Example : Edit the 'servers' file and add something like : </p>
+<div><pre>
+[global]
+http-proxy-host = your.proxy.name
+http-proxy-port = 3128
+</pre></div>
+<p>Please use the regular http proxy settings in case you want to access the the repository from the Sun network (SWAN). </p>
+
+</div>
+
+<div class="section"><h3>Committer access<a name="Committer_access"></a></h3>
+
+<p>Everyone can access the Apache JDO Subversion repository via HTTPS, but Apache JDO Committers must checkout the Subversion repository via HTTPS. </p>
+<div><pre>
+% svn checkout https://svn.apache.org/repos/asf/db/jdo
+</pre></div>
+</div>
+<div class="section"><h3>NetBeans CVS repository access<a name="NetBeans_CVS_repository_access"></a></h3>
+
+<p>The btree subproject checks out the NetBeans mdr btree implementation. This requires cvs being installed on your system. The official NetBeans cvs host might not work if you are behind a firewall that blocks the cvs port. Please consult the <a class="external" href="http://www.netbeans.org/community/sources" rel="nofollow">NetBeans sources</a> page for more info.  </p>
+<p>If you do not have a cvs client installed on your system you can download the NetBeans mdr btree sources <a href="/jdo-data/attachments/SubversionRepository/attachments/netbeans-mdr-btree.zip">here</a>. Unzip the file in the btree directory and comment out (or remove) the definition of the preGoal java:prepare-filesystem. </p>
+</div>
+</div>
+
+<div class="section"><h2>Submitting Code Changes<a name="Submitting_Code_Changes"></a></h2>
+<div class="section"><h3>Submitting a patch<a name="Submitting_a_patch"></a></h3>
+
+<p>If you make changes to Apache JDO, and would like to contribute the to the project, you should create a patch and send it to the jdo-dev alias <a class="externalLink" href="mailto:jdo-dev@db.apache.org">jdo-dev@db.apache.org</a>.  To create a patch, simply execute the following command: </p>
+<div><pre>
+% svn diff &gt; your-changes.patch
+</pre></div>
+</div>
+
+<div class="section"><h3>Committing changes to subversion<a name="Committing_changes_to_subversion"></a></h3>
+<p>
+To commit changes to the Subversion repository, you must be an Apache JDO committer.  See <a href="get-involved.html">Get Involved</a> for information on how to become a committer and how to set up your password once you become a committer.
+</p>
+
+<p>
+Once your password is set, you can use a command like this to commit:
+</p>
+<div><pre>
+$&gt; svn commit --username your-username
+Authentication realm: &lt;https://svn.apache.org:443&gt; ASF Committers
+Password for 'your-username': your-password
+</pre></div>
+<p>You can also pass your password on the command line directly, but this is a security problem on multiuser unix computers (the command line arguments are available via the ps command).  Here is the command if you are Windows or a single user unix computer: </p>
+<div><pre>
+$&gt; svn commit --username your-username --password your-password
+</pre></div>
+<p>Remember to replace 'your-username' and 'your-password' with your actual username and password on svn.apache.org. </p>
+
+</div>
+</div>
+
+<div class="section"><h2>Building JDO from Source<a name="Building_JDO_from_Source"></a></h2>
+<p>Refer to the <a class="externalLink" href="http://wiki.apache.org/jdo/FrontPage">Wiki
+page</a> for details. Note that the JDO project is subdivided into several
+smaller projects, and each project is built separately. </p>
+
+</div>
+
+<div class="section"><h2>Using Subversion on Windows with cygwin<a name="Using_Subversion_on_Windows_with_cygwin"></a></h2>
+
+<p>If you use Subversion on Windows under cygwin, you may find that the Subversion client automatically assigns the executable property to non-executable files. In that case, you would see this at the bottom of an <i>svn diff</i> of the file: 
+</p>
+<div><pre>
+Property changes on: test/sql/derby/datastoreidentity/schema1.sql
+___________________________________________________________________
+Name: svn:executable
+   + *
+</pre></div>
+<p>This section explains the source of the problem and suggests some actions to avoid it. </p>
+
+<div class="section"><h3>Background<a name="Background"></a></h3>
+
+<p>Subversion carries executable information in the built-in property called svn:executable.  This property, unlike others,  may be present or absent, but it has no value.  You can add it or delete it, but but you cannot change its value. </p>
+<p>In theory, Subversion ignores Windows file permissions and by default does not set svn:executable. However, cygwin svn acts like Unix svn and determines the svn:executable property based on file permissions. </p>
+<p>If you create a file from the cygwin command line, by default it is executable only if the filename ends with .bat, .com or .exe, or if its content starts with #!. [This is what the doc says, but you may see -x for all files.] If you create a file using a Windows tool, by default its Windows permissions are executable by all. Cygwin interprets the Unix-style permissions this way as well. If the file is executable by all, cygwin svn sets the svn:executable property on the file when you invoke <i>svn add</i>. </p>
+</div>
+<div class="section"><h3>Removing existing executable properties from the repository<a name="Removing_existing_executable_properties_from_the_repository"></a></h3>
+
+<p>You can use svn propdel to remove the svn:executable property from your working copy. 
+</p>
+<div><pre>
+    svn propdel -R svn:executable .
+</pre></div>
+<p>will recursively remove the svn:executable property from all of the files below the current directory.  You can use this and commit the files to clean the repository if necessary. </p>
+
+</div>
+<div class="section"><h3>Preventing Subversion from adding unwanted executable properties<a name="Preventing_Subversion_from_adding_unwanted_executable_properties"></a></h3>
+
+<p>Windows/cygwin users who don't want to have to think about using <i>svn propdel</i> or <i>chmod</i> on each added file can use a non-cygwin version of svn. The Subversion 1.2.3 Win32 binaries, downloadable from the link at the bottom of <a class="externalLink" href="http://subversion.tigris.org/project_packages.html" rel="nofollow">http://subversion.tigris.org/project_packages.html</a>, appear to work well. After installation add the svn.exe location to your Windows PATH variable. If you are switching from cygwin svn to Win32 svn </p>
+<ol style="list-style-type: decimal">
+<li><p>Remove the subversion component from your cygwin installation because when svn is invoked from a cygwin window, the cygwin version is found even if your cygwin/bin directory is later on the path. (In the Select Packages window of the setup wizard, navigate to the subversion package in the Devel. category.  Click on the status icon until Uninstall is displayed. Click next and continue through the wizard until installation is complete.) </p>
+
+</li>
+<li><p>Copy the servers file and the auth folder from the sygwin ~/.subversion directory to C:\Documents and Settings\&lt;user&gt;\Application Data\Subversion used by Win32 subversion. </p>
+</li>
+</ol>
+<p>Note that windows svn uses backslash as the path separator when displaying file names. You cannot just copy and paste this file name to another svn command when running from within a cygwin shell. You need to enclose the file name into double quotes. </p>
+<p>Alternatively, Windows users can set file permissions in Windows Explorer. (Right-click on the top-level folder &amp; select Properties. Select the Security tab. Click Advanced. Remove all instances of Read &amp; Execute from the Permission Entries. Click &quot;Reset permissions on all child objects and enable propogations of inheritable permissions&quot;. Click Apply. OK. OK.) You will have to do this again when you do a clean checkout to a new directory. </p>
+
+</div>
+</div>
+
 
       </div>
     </div>
@@ -391,7 +391,7 @@ Name: svn:executable
     </div>
     <div id="footer">
       <div class="xright">
-              Copyright &#169;                   2005-2013.
+              Copyright &#169;                   2005-2014.
           All Rights Reserved.      
                     
                   </div>

Modified: websites/production/db/content/jdo/tck.html
==============================================================================
--- websites/production/db/content/jdo/tck.html (original)
+++ websites/production/db/content/jdo/tck.html Sun Jan  5 10:08:45 2014
@@ -1,5 +1,5 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia Site Renderer 1.3 at Nov 4, 2013 -->
+<!-- Generated by Apache Maven Doxia Site Renderer 1.3 at Jan 5, 2014 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
   <head>
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
@@ -12,7 +12,7 @@
     </style>
     <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
       <meta name="author" content="JDO Documentation Team" />
-    <meta name="Date-Revision-yyyymmdd" content="20131104" />
+    <meta name="Date-Revision-yyyymmdd" content="20140105" />
     <meta http-equiv="Content-Language" content="en" />
         
         </head>
@@ -102,7 +102,7 @@
                   <li class="none">
                           <a href="field_types.html" title="Types of Fields">Types of Fields</a>
             </li>
-                                                                                                                          <li class="collapsed">
+                                                                                                                                            <li class="collapsed">
                           <a href="metadata.html" title="MetaData">MetaData</a>
                   </li>
                   <li class="none">
@@ -210,63 +210,63 @@
     </div>
     <div id="bodyColumn">
       <div id="contentBox">
-        <!-- Licensed to the Apache Software Foundation (ASF) under one or more
-contributor license agreements.  See the NOTICE file distributed with
-this work for additional information regarding copyright ownership.
-The ASF licenses this file to You under the Apache License, Version 2.0
-(the "License"); you may not use this file except in compliance with
-the License.  You may obtain a copy of the License at
-
-    http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software 
-distributed under the License is distributed on an "AS IS" BASIS, 
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 
-See the License for the specific language governing permissions and 
-limitations under the License. -->
-
- 
-
-<div class="section"><h2>About the Technology Compatibility Kit<a name="About_the_Technology_Compatibility_Kit"></a></h2>
-
-<p>
-    In order to demonstrate compliance with the Java Data Objects specification,
-    an implementation must pass all of the tests in the Technology Compatibility Kit (TCK).
-    The TCK is released as a packaged Java source tree.
-    Maven is the driver of a test run. You must download and install 
-    <a class="externalLink" href="http://maven.apache.org/">Maven 2+</a>before running the TCK.
-</p>
-</div>
-
-<div class="section"><h2>Running the TCK<a name="Running_the_TCK"></a></h2>
-    <p>
-        To run the Technology Compatibility Kit:
-    </p>
-    <ol style="list-style-type: decimal">
-        <li>
-        Check out the JDO source code from the most recent branch. See <a class="externalLink" href="http://db.apache.org/jdo/svn.html">Source Code</a> for instructions on checking out code.
-        </li>
-        <li>
-        Follow the instructions in the Prerequisites section of 
-        <a class="externalLink" href="http://svn.apache.org/viewcvs.cgi/*checkout*/db/jdo/branches/3.1-rc1/README.html">README.html</a>.
-        </li>
-        <li>
-        Follow the procedure in <a class="externalLink" href="http://svn.apache.org/viewcvs.cgi/*checkout*/db/jdo/branches/3.1-rc1/tck/RunRules.html">RunRules.html</a> in the tck directory.
-        </li>
-    </ol>
-</div>
-
-<div class="section"><h2>Demonstrating Compliance<a name="Demonstrating_Compliance"></a></h2>
-<p>
-Vendors must post test results on a publicly accessible web site for
-examination by the public. The posting includes the output of the
-test run, which consists of multiple log files containing
-configuration information and test results. For an example of the
-required posting, please see <a href="tck/final">http://db.apache.org/jdo/tck/final</a>.
-</p>
-</div>
-
-
+        <!-- Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software 
+distributed under the License is distributed on an "AS IS" BASIS, 
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 
+See the License for the specific language governing permissions and 
+limitations under the License. -->
+
+ 
+
+<div class="section"><h2>About the Technology Compatibility Kit<a name="About_the_Technology_Compatibility_Kit"></a></h2>
+
+<p>
+    In order to demonstrate compliance with the Java Data Objects specification,
+    an implementation must pass all of the tests in the Technology Compatibility Kit (TCK).
+    The TCK is released as a packaged Java source tree.
+    Maven is the driver of a test run. You must download and install 
+    <a class="externalLink" href="http://maven.apache.org/">Maven 2+</a>before running the TCK.
+</p>
+</div>
+
+<div class="section"><h2>Running the TCK<a name="Running_the_TCK"></a></h2>
+    <p>
+        To run the Technology Compatibility Kit:
+    </p>
+    <ol style="list-style-type: decimal">
+        <li>
+        Check out the JDO source code from the most recent branch. See <a class="externalLink" href="http://db.apache.org/jdo/svn.html">Source Code</a> for instructions on checking out code.
+        </li>
+        <li>
+        Follow the instructions in the Prerequisites section of 
+        <a class="externalLink" href="http://svn.apache.org/viewcvs.cgi/*checkout*/db/jdo/branches/3.1-rc1/README.html">README.html</a>.
+        </li>
+        <li>
+        Follow the procedure in <a class="externalLink" href="http://svn.apache.org/viewcvs.cgi/*checkout*/db/jdo/branches/3.1-rc1/tck/RunRules.html">RunRules.html</a> in the tck directory.
+        </li>
+    </ol>
+</div>
+
+<div class="section"><h2>Demonstrating Compliance<a name="Demonstrating_Compliance"></a></h2>
+<p>
+Vendors must post test results on a publicly accessible web site for
+examination by the public. The posting includes the output of the
+test run, which consists of multiple log files containing
+configuration information and test results. For an example of the
+required posting, please see <a href="tck/final">http://db.apache.org/jdo/tck/final</a>.
+</p>
+</div>
+
+
 
       </div>
     </div>
@@ -275,7 +275,7 @@ required posting, please see <a href="tc
     </div>
     <div id="footer">
       <div class="xright">
-              Copyright &#169;                   2005-2013.
+              Copyright &#169;                   2005-2014.
           All Rights Reserved.      
                     
                   </div>

Modified: websites/production/db/content/jdo/team-list.html
==============================================================================
--- websites/production/db/content/jdo/team-list.html (original)
+++ websites/production/db/content/jdo/team-list.html Sun Jan  5 10:08:45 2014
@@ -1,5 +1,5 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia Site Renderer 1.3 at Nov 4, 2013 -->
+<!-- Generated by Apache Maven Doxia Site Renderer 1.3 at Jan 5, 2014 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
   <head>
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
@@ -12,7 +12,7 @@
     </style>
     <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
       <meta name="author" content="Apache JDO Development Team" />
-    <meta name="Date-Revision-yyyymmdd" content="20131104" />
+    <meta name="Date-Revision-yyyymmdd" content="20140105" />
     <meta http-equiv="Content-Language" content="en" />
         
         </head>
@@ -102,7 +102,7 @@
                   <li class="none">
                           <a href="field_types.html" title="Types of Fields">Types of Fields</a>
             </li>
-                                                                                                                          <li class="collapsed">
+                                                                                                                                            <li class="collapsed">
                           <a href="metadata.html" title="MetaData">MetaData</a>
                   </li>
                   <li class="none">
@@ -210,71 +210,71 @@
     </div>
     <div id="bodyColumn">
       <div id="contentBox">
-        <!-- Licensed to the Apache Software Foundation (ASF) under one or more
-contributor license agreements.  See the NOTICE file distributed with
-this work for additional information regarding copyright ownership.
-The ASF licenses this file to You under the Apache License, Version 2.0
-(the "License"); you may not use this file except in compliance with
-the License.  You may obtain a copy of the License at
-
-    http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software 
-distributed under the License is distributed on an "AS IS" BASIS, 
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 
-See the License for the specific language governing permissions and 
-limitations under the License. -->
-
- 
-
-<div class="section"><h2>The Apache JDO Team<a name="The_Apache_JDO_Team"></a></h2>
-
-<p>
-    The people listed below have made significant contributions to JDO by
-    working long and hard to make quality software for the rest of the world to
-    use.
-</p>
-
-<p>
-    If you would like to contribute to JDO, please see the
-    <a href="roadmap.html">roadmap</a> list to find areas where you 
-    can contribute.
-    If there is nothing in there that suits your interest, but you still have
-    ideas, please feel free to suggest them on the mailing list.
-</p>
-<p>
-    If you would like to become a committer, please see
-    <a href="get-involved.html">Get Involved</a>.
-</p>
-
-</div>
-<div class="section"><h2>Apache JDO Committers<a name="Apache_JDO_Committers"></a></h2>
-<table border="0" class="bodyTable">
-<tr class="a"><th>Name</th><th>Organization</th></tr>
-<tr class="b"><td>Matthew Adams</td><td>SpringSource</td></tr>
-<tr class="a"><td>Erik Bengtson</td><td>JPOX</td></tr>
-<tr class="b"><td>Michael Bouschen</td><td>Tech@Spree</td></tr>
-<tr class="a"><td>Michelle Caisse</td><td>Sun Microsystems, Inc.</td></tr>
-<tr class="b"><td>Andy Jefferson</td><td>DataNucleus</td></tr>
-<tr class="a"><td>Patrick Linskey</td><td>Oracle</td></tr>
-<tr class="b"><td>Geir Magnusson Jr.</td><td>IBM</td></tr>
-<tr class="a"><td>Brian McCallister</td><td></td></tr>
-<tr class="b"><td>Craig Russell</td><td>Sun Microsystems, Inc.</td></tr>
-<tr class="a"><td>Dain Sundstrom</td><td></td></tr>
-<tr class="b"><td>Brian Topping</td><td></td></tr>
-<tr class="a"><td>Michael Watzek</td><td>Tech@Spree</td></tr>
-<tr class="b"><td>Martin Zaun</td><td>Sun Microsystems, Inc.</td></tr>
-</table>
-</div>
-
-<div class="section"><h2>Apache JDO Contributors<a name="Apache_JDO_Contributors"></a></h2>
-<table border="0" class="bodyTable">
-<tr class="a"><th>Name</th><th>Organization</th></tr>
-<tr class="b"><td>Chris Beams</td><td>SpringSource</td></tr>
-<tr class="a"><td>Ilan Kirsch</td><td>ObjectDB</td></tr>
-</table>
-</div>
-
+        <!-- Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software 
+distributed under the License is distributed on an "AS IS" BASIS, 
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 
+See the License for the specific language governing permissions and 
+limitations under the License. -->
+
+ 
+
+<div class="section"><h2>The Apache JDO Team<a name="The_Apache_JDO_Team"></a></h2>
+
+<p>
+    The people listed below have made significant contributions to JDO by
+    working long and hard to make quality software for the rest of the world to
+    use.
+</p>
+
+<p>
+    If you would like to contribute to JDO, please see the
+    <a href="roadmap.html">roadmap</a> list to find areas where you 
+    can contribute.
+    If there is nothing in there that suits your interest, but you still have
+    ideas, please feel free to suggest them on the mailing list.
+</p>
+<p>
+    If you would like to become a committer, please see
+    <a href="get-involved.html">Get Involved</a>.
+</p>
+
+</div>
+<div class="section"><h2>Apache JDO Committers<a name="Apache_JDO_Committers"></a></h2>
+<table border="0" class="bodyTable">
+<tr class="a"><th>Name</th><th>Organization</th></tr>
+<tr class="b"><td>Matthew Adams</td><td>SpringSource</td></tr>
+<tr class="a"><td>Erik Bengtson</td><td>JPOX</td></tr>
+<tr class="b"><td>Michael Bouschen</td><td>Tech@Spree</td></tr>
+<tr class="a"><td>Michelle Caisse</td><td>Sun Microsystems, Inc.</td></tr>
+<tr class="b"><td>Andy Jefferson</td><td>DataNucleus</td></tr>
+<tr class="a"><td>Patrick Linskey</td><td>Oracle</td></tr>
+<tr class="b"><td>Geir Magnusson Jr.</td><td>IBM</td></tr>
+<tr class="a"><td>Brian McCallister</td><td></td></tr>
+<tr class="b"><td>Craig Russell</td><td>Sun Microsystems, Inc.</td></tr>
+<tr class="a"><td>Dain Sundstrom</td><td></td></tr>
+<tr class="b"><td>Brian Topping</td><td></td></tr>
+<tr class="a"><td>Michael Watzek</td><td>Tech@Spree</td></tr>
+<tr class="b"><td>Martin Zaun</td><td>Sun Microsystems, Inc.</td></tr>
+</table>
+</div>
+
+<div class="section"><h2>Apache JDO Contributors<a name="Apache_JDO_Contributors"></a></h2>
+<table border="0" class="bodyTable">
+<tr class="a"><th>Name</th><th>Organization</th></tr>
+<tr class="b"><td>Chris Beams</td><td>SpringSource</td></tr>
+<tr class="a"><td>Ilan Kirsch</td><td>ObjectDB</td></tr>
+</table>
+</div>
+
 
       </div>
     </div>
@@ -283,7 +283,7 @@ limitations under the License. -->
     </div>
     <div id="footer">
       <div class="xright">
-              Copyright &#169;                   2005-2013.
+              Copyright &#169;                   2005-2014.
           All Rights Reserved.      
                     
                   </div>

Modified: websites/production/db/content/jdo/transactions.html
==============================================================================
--- websites/production/db/content/jdo/transactions.html (original)
+++ websites/production/db/content/jdo/transactions.html Sun Jan  5 10:08:45 2014
@@ -1,5 +1,5 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia Site Renderer 1.3 at Nov 4, 2013 -->
+<!-- Generated by Apache Maven Doxia Site Renderer 1.3 at Jan 5, 2014 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
   <head>
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
@@ -11,7 +11,7 @@
       @import url("./css/site.css");
     </style>
     <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
-    <meta name="Date-Revision-yyyymmdd" content="20131104" />
+    <meta name="Date-Revision-yyyymmdd" content="20140105" />
     <meta http-equiv="Content-Language" content="en" />
         
         </head>
@@ -101,7 +101,7 @@
                   <li class="none">
                           <a href="field_types.html" title="Types of Fields">Types of Fields</a>
             </li>
-                                                                                                                          <li class="collapsed">
+                                                                                                                                            <li class="collapsed">
                           <a href="metadata.html" title="MetaData">MetaData</a>
                   </li>
                   <li class="none">
@@ -209,51 +209,51 @@
     </div>
     <div id="bodyColumn">
       <div id="contentBox">
-        
-    
-        <div class="section"><h2>Transactions<a name="Transactions"></a></h2>
-            <p>
-                When managing the persistence of objects using a <a href="pm.html">PersistenceManager</a>
-                it is normal to handle all datastore operations in a transaction. For this reason each
-                <i>PersistenceManager</i> has its own transaction. Consequently a typical JDO persistence method
-                will look something like this
-            </p>
-            <div class="source"><pre>
-PersistenceManager pm = pmf.getPersistenceManager();
-Transaction tx = pm.currentTransaction();
-try
-{
-    tx.begin(); // Start the PM transaction
-
-    ... perform some persistence operations
-
-    tx.commit(); // Commit the PM transaction
-}
-finally
-{
-    if (tx.isActive())
-    {
-        tx.rollback(); // Error occurred so rollback the PM transaction
-    }
-}</pre></div>
-            <p>
-                JDO supports the two main forms of transaction
-            </p>
-            <ul>
-                <li>Transactions can lock all records in a datastore and keep them locked until they are 
-                    ready to commit their changes. These are known as Pessimistic (or datastore) 
-                    Transactions</li>
-                <li>Transactions can simply assume that things in the datastore will not change until they 
-                    are ready to commit, not lock any records and then just before committing make a check 
-                    for changes. These are known as Optimistic Transactions.</li>
-            </ul>
-            <p>
-                You select the type of transaction to be used by a <i>PersistenceManager</i> (PM) either by
-                setting the PMF property <b>javax.jdo.option.Optimistic</b>, or on the transaction you call
-            </p>
-            <div class="source"><pre>pm.currentTransaction().setOptimistic(true);</pre></div>
-        </div>
-    
+        
+    
+        <div class="section"><h2>Transactions<a name="Transactions"></a></h2>
+            <p>
+                When managing the persistence of objects using a <a href="pm.html">PersistenceManager</a>
+                it is normal to handle all datastore operations in a transaction. For this reason each
+                <i>PersistenceManager</i> has its own transaction. Consequently a typical JDO persistence method
+                will look something like this
+            </p>
+            <div class="source"><pre>
+PersistenceManager pm = pmf.getPersistenceManager();
+Transaction tx = pm.currentTransaction();
+try
+{
+    tx.begin(); // Start the PM transaction
+
+    ... perform some persistence operations
+
+    tx.commit(); // Commit the PM transaction
+}
+finally
+{
+    if (tx.isActive())
+    {
+        tx.rollback(); // Error occurred so rollback the PM transaction
+    }
+}</pre></div>
+            <p>
+                JDO supports the two main forms of transaction
+            </p>
+            <ul>
+                <li>Transactions can lock all records in a datastore and keep them locked until they are 
+                    ready to commit their changes. These are known as Pessimistic (or datastore) 
+                    Transactions</li>
+                <li>Transactions can simply assume that things in the datastore will not change until they 
+                    are ready to commit, not lock any records and then just before committing make a check 
+                    for changes. These are known as Optimistic Transactions.</li>
+            </ul>
+            <p>
+                You select the type of transaction to be used by a <i>PersistenceManager</i> (PM) either by
+                setting the PMF property <b>javax.jdo.option.Optimistic</b>, or on the transaction you call
+            </p>
+            <div class="source"><pre>pm.currentTransaction().setOptimistic(true);</pre></div>
+        </div>
+    
 
       </div>
     </div>
@@ -262,7 +262,7 @@ finally
     </div>
     <div id="footer">
       <div class="xright">
-              Copyright &#169;                   2005-2013.
+              Copyright &#169;                   2005-2014.
           All Rights Reserved.      
                     
                   </div>

Modified: websites/production/db/content/jdo/why_jdo.html
==============================================================================
--- websites/production/db/content/jdo/why_jdo.html (original)
+++ websites/production/db/content/jdo/why_jdo.html Sun Jan  5 10:08:45 2014
@@ -1,5 +1,5 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia Site Renderer 1.3 at Nov 4, 2013 -->
+<!-- Generated by Apache Maven Doxia Site Renderer 1.3 at Jan 5, 2014 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
   <head>
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
@@ -11,7 +11,7 @@
       @import url("./css/site.css");
     </style>
     <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
-    <meta name="Date-Revision-yyyymmdd" content="20131104" />
+    <meta name="Date-Revision-yyyymmdd" content="20140105" />
     <meta http-equiv="Content-Language" content="en" />
         
         </head>
@@ -101,7 +101,7 @@
                   <li class="none">
                           <a href="field_types.html" title="Types of Fields">Types of Fields</a>
             </li>
-                                                                                                                          <li class="collapsed">
+                                                                                                                                            <li class="collapsed">
                           <a href="metadata.html" title="MetaData">MetaData</a>
                   </li>
                   <li class="none">
@@ -209,164 +209,164 @@
     </div>
     <div id="bodyColumn">
       <div id="contentBox">
-        
-    
-        <div class="section"><h2>Why JDO ?<a name="Why_JDO_"></a></h2>
-            <p>
-                The majority of applications need to persist (or store) data during their lifecycle. 
-                There are many ways of doing this with an application written in Java.
-            </p>
-            <ul>
-                <li>If your datastore is RDBMS you can handle the persistence (and retrieval) of data yourself
-                    using <b>JDBC</b>. Obviously with this route you have the burden of having to write the 
-                    persistence layer yourself. This gives much control, but also creates significant work,
-                    both in writing the code but also in testing and maintenance.</li>
-                <li>You can use <b>JDO</b>, a standardised persistence API. With <b>JDO</b> you can develop
-                    plain old java objects (POJOs) and persist them as they are transparently. This requires
-                    very little work from the developer. It allows persistence to any type of datastore in
-                    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>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. It really
-                    only allows persistence to RDBMS datastores. If you want to persist to other datastores
-                    you should consider JDO.</li>
-                <li><i>If you are stuck with using an EJB2.* architecture you could use Entity Beans. This 
-                    means that you hand off your objects to the EJB part of the J2EE server. This simplifies 
-                    things for the developer in some respect but places major restrictions in that your objects 
-                    have to be Entity Beans.</i></li>
-                <li>You can also use a proprietary persistence API (e.g Hibernates own API, TopLinks own API, iBatis, Castor etc).
-                    The disadvantages of going this route are that you cannot easily swap to an alternative
-                    implementation of the API if you hit problems with your software choice.</li>
-            </ul>
-            <p>
-                To give a <i>guide</i>, here are a few important consideration points when choosing a persistence layer for your application.
-            </p>
-
-            <table border="0" class="bodyTable">
-                <tr class="a">
-                    <th>Feature</th>
-                    <th width="100">JDBC</th>
-                    <th width="100">JDO</th>
-                    <th width="100">JPA</th>
-                    <th width="100">EJB2</th>
-                    <th width="100">Custom ORM</th>
-                </tr>
-                <tr class="b">
-                    <td>Standards-Driven</td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_error_sml.gif" alt="" border="0" /></td>
-                </tr>
-                <tr class="a">
-                    <td>Choice of datastores</td>
-                    <td><img src="images/icon_error_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_error_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_error_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                </tr>
-                <tr class="b">
-                    <td>Support POJOs</td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_error_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                </tr>
-                <tr class="a">
-                    <td>Usable in J2SE</td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_error_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                </tr>
-                <tr class="b">
-                    <td>Usable in J2EE</td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                </tr>
-                <tr class="a">
-                    <td>Out of box implementation (1)</td>
-                    <td><img src="images/icon_error_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_error_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                </tr>
-                <tr class="b">
-                    <td>Simple to unit test</td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_error_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                </tr>
-                <tr class="a">
-                    <td>Dynamic queries</td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /> (2)</td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_error_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                </tr>
-                <tr class="b">
-                    <td>Comprehensive ORM</td>
-                    <td><img src="images/icon_warning_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_warning_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_error_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                </tr>
-                <tr class="a">
-                    <td>Primary Key generation</td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /> (2)</td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                </tr>
-                <tr class="b">
-                    <td>Supports inherited objects</td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /> (2)</td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                </tr>
-                <tr class="a">
-                    <td>Schema Creation</td>
-                    <td><img src="images/icon_error_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                </tr>                
-                <tr class="b">
-                    <td>Existing schema</td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
-                </tr>
-            </table>
-            <ol style="list-style-type: decimal">
-                <li>refers to whether it is necessary to write the persistence yourself (e.g as with JDBC) or 
-                    whether you can just persist by simple calls.</li>
-                <li>requires the developer to write this layer.</li>
-            </ol>
-        </div>
-
-    
+        
+    
+        <div class="section"><h2>Why JDO ?<a name="Why_JDO_"></a></h2>
+            <p>
+                The majority of applications need to persist (or store) data during their lifecycle. 
+                There are many ways of doing this with an application written in Java.
+            </p>
+            <ul>
+                <li>If your datastore is RDBMS you can handle the persistence (and retrieval) of data yourself
+                    using <b>JDBC</b>. Obviously with this route you have the burden of having to write the 
+                    persistence layer yourself. This gives much control, but also creates significant work,
+                    both in writing the code but also in testing and maintenance.</li>
+                <li>You can use <b>JDO</b>, a standardised persistence API. With <b>JDO</b> you can develop
+                    plain old java objects (POJOs) and persist them as they are transparently. This requires
+                    very little work from the developer. It allows persistence to any type of datastore in
+                    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>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. It really
+                    only allows persistence to RDBMS datastores. If you want to persist to other datastores
+                    you should consider JDO.</li>
+                <li><i>If you are stuck with using an EJB2.* architecture you could use Entity Beans. This 
+                    means that you hand off your objects to the EJB part of the J2EE server. This simplifies 
+                    things for the developer in some respect but places major restrictions in that your objects 
+                    have to be Entity Beans.</i></li>
+                <li>You can also use a proprietary persistence API (e.g Hibernates own API, TopLinks own API, iBatis, Castor etc).
+                    The disadvantages of going this route are that you cannot easily swap to an alternative
+                    implementation of the API if you hit problems with your software choice.</li>
+            </ul>
+            <p>
+                To give a <i>guide</i>, here are a few important consideration points when choosing a persistence layer for your application.
+            </p>
+
+            <table border="0" class="bodyTable">
+                <tr class="a">
+                    <th>Feature</th>
+                    <th width="100">JDBC</th>
+                    <th width="100">JDO</th>
+                    <th width="100">JPA</th>
+                    <th width="100">EJB2</th>
+                    <th width="100">Custom ORM</th>
+                </tr>
+                <tr class="b">
+                    <td>Standards-Driven</td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_error_sml.gif" alt="" border="0" /></td>
+                </tr>
+                <tr class="a">
+                    <td>Choice of datastores</td>
+                    <td><img src="images/icon_error_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_error_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_error_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                </tr>
+                <tr class="b">
+                    <td>Support POJOs</td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_error_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                </tr>
+                <tr class="a">
+                    <td>Usable in J2SE</td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_error_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                </tr>
+                <tr class="b">
+                    <td>Usable in J2EE</td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                </tr>
+                <tr class="a">
+                    <td>Out of box implementation (1)</td>
+                    <td><img src="images/icon_error_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_error_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                </tr>
+                <tr class="b">
+                    <td>Simple to unit test</td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_error_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                </tr>
+                <tr class="a">
+                    <td>Dynamic queries</td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /> (2)</td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_error_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                </tr>
+                <tr class="b">
+                    <td>Comprehensive ORM</td>
+                    <td><img src="images/icon_warning_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_warning_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_error_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                </tr>
+                <tr class="a">
+                    <td>Primary Key generation</td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /> (2)</td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                </tr>
+                <tr class="b">
+                    <td>Supports inherited objects</td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /> (2)</td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                </tr>
+                <tr class="a">
+                    <td>Schema Creation</td>
+                    <td><img src="images/icon_error_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                </tr>                
+                <tr class="b">
+                    <td>Existing schema</td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                    <td><img src="images/icon_success_sml.gif" alt="" border="0" /></td>
+                </tr>
+            </table>
+            <ol style="list-style-type: decimal">
+                <li>refers to whether it is necessary to write the persistence yourself (e.g as with JDBC) or 
+                    whether you can just persist by simple calls.</li>
+                <li>requires the developer to write this layer.</li>
+            </ol>
+        </div>
+
+    
 
       </div>
     </div>
@@ -375,7 +375,7 @@
     </div>
     <div id="footer">
       <div class="xright">
-              Copyright &#169;                   2005-2013.
+              Copyright &#169;                   2005-2014.
           All Rights Reserved.      
                     
                   </div>



Mime
View raw message