Added:
websites/production/openjpa/content/builds/2.4.2/apache-openjpa/docs/introduction.html
==============================================================================
---
websites/production/openjpa/content/builds/2.4.2/apache-openjpa/docs/introduction.html
(added)
+++
websites/production/openjpa/content/builds/2.4.2/apache-openjpa/docs/introduction.html
Fri Jan 6 19:19:20 2017
@@ -0,0 +1,25 @@
+<html><head>
+ <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+ <title>Part 1. Introduction</title><base href="display"><link
rel="stylesheet" type="text/css" href="css/docbook.css"><meta name="generator"
content="DocBook XSL Stylesheets V1.79.1"><link rel="home" href="manual.html"
title="Apache OpenJPA 2.4 User's Guide"><link rel="up" href="manual.html"
title="Apache OpenJPA 2.4 User's Guide"><link rel="prev" href="manual.html"
title="Apache OpenJPA 2.4 User's Guide"><link rel="next"
href="openjpa_intro.html" title="Chapter 1. About"></head><body
bgcolor="white" text="black" link="#0000FF" vlink="#840084"
alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation
header"><tr><th colspan="3"
align="center">Part 1. Introduction</th></tr><tr><td width="20%"
align="left"><a accesskey="p" href="manual.html">Prev</a> </td><th
width="60%" align="center"> </th><td width="20%" align="right"> <a
accesskey="n"
href="openjpa_intro.html">Next</a></td></tr></table><hr></div><div class="part
" id="introduction"><div class="titlepage"><div><div><h1
class="title">Part 1. Introduction</h1></div></div></div><div
class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span
class="chapter"><a href="openjpa_intro.html">1.
+ About
+ </a></span></dt><dt><span class="chapter"><a href="openjpa_legal.html">2.
+ Legal
+ </a></span></dt><dd><dl><dt><span class="section"><a
href="openjpa_legal.html#openjpa_legal_license">1.
+ License
+ </a></span></dt><dt><span class="section"><a
href="openjpa_legal_notice.html">2.
+ Notice
+ </a></span></dt><dt><span class="section"><a
href="openjpa_legal_copyright.html">3.
+ Copyrights
+ </a></span></dt><dd><dl><dt><span class="section"><a
href="openjpa_legal_copyright.html#openjpa_legal_copyright_apache">3.1.
Apache</a></span></dt><dt><span class="section"><a
href="openjpa_legal_copyright.html#openjpa_legal_copyright_serp">3.2.
Serp</a></span></dt><dt><span class="section"><a
href="openjpa_legal_copyright.html#openjpa_legal_copyright_sun">3.3.
Sun</a></span></dt><dt><span class="section"><a
href="openjpa_legal_copyright.html#openjpa_legal_copyright_other">3.4.
Other</a></span></dt></dl></dd></dl></dd></dl></div>
+
+
+
+
+
+
+
+
+
+ </div><div class="navfooter"><hr><table width="100%" summary="Navigation
footer"><tr><td width="40%" align="left"><a accesskey="p"
href="manual.html">Prev</a> </td><td width="20%"
align="center"> </td><td width="40%" align="right"> <a accesskey="n"
href="openjpa_intro.html">Next</a></td></tr><tr><td width="40%" align="left"
valign="top">Apache OpenJPA 2.4 User's Guide </td><td width="20%"
align="center"><a accesskey="h" href="manual.html">Home</a></td><td width="40%"
align="right" valign="top"> Chapter 1.
+ About
+ </td></tr></table></div></body></html>
\ No newline at end of file
Added:
websites/production/openjpa/content/builds/2.4.2/apache-openjpa/docs/jpa_2.2.html
==============================================================================
---
websites/production/openjpa/content/builds/2.4.2/apache-openjpa/docs/jpa_2.2.html
(added)
+++
websites/production/openjpa/content/builds/2.4.2/apache-openjpa/docs/jpa_2.2.html
Fri Jan 6 19:19:20 2017
@@ -0,0 +1,207 @@
+<html><head>
+ <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+ <title>2. OpenJPA 2.2.0</title><base href="display"><link
rel="stylesheet" type="text/css" href="css/docbook.css"><meta name="generator"
content="DocBook XSL Stylesheets V1.79.1"><link rel="home" href="manual.html"
title="Apache OpenJPA 2.4 User's Guide"><link rel="up"
href="migration_considerations.html" title="Appendix 3. Migration
Considerations"><link rel="prev" href="migration_considerations.html"
title="Appendix 3. Migration Considerations"><link rel="next"
href="jpa_2.3.html" title="3. OpenJPA 2.3.0"></head><body bgcolor="white"
text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div
class="navheader"><table width="100%" summary="Navigation header"><tr><th
colspan="3" align="center">2.
+ OpenJPA 2.2.0
+ </th></tr><tr><td width="20%" align="left"><a accesskey="p"
href="migration_considerations.html">Prev</a> </td><th width="60%"
align="center">Appendix 3.
+ Migration Considerations
+ </th><td width="20%" align="right"> <a accesskey="n"
href="jpa_2.3.html">Next</a></td></tr></table><hr></div><div class="section"
id="jpa_2.2"><div class="titlepage"><div><div><h2 class="title" style="clear:
both">2.
+ OpenJPA 2.2.0
+ </h2></div></div></div><div class="toc"><dl class="toc"><dt><span
class="section"><a href="jpa_2.2.html#jpa_2.2_incompatibilities">2.1.
Incompatibilities</a></span></dt><dd><dl><dt><span class="section"><a
href="jpa_2.2.html#jpa_2.2_allocationSize">2.1.1.
+ allocationSize Property of Sequence Generator
+ </a></span></dt><dt><span class="section"><a
href="jpa_2.2.html#jpa_2.2_metamodelArrays">2.1.2.
+ MetaModel Attributes for Arrays
+ </a></span></dt><dt><span class="section"><a
href="jpa_2.2.html#jpa_2.2_SupportsSetClob">2.1.3.
+ supportsSetClob Property.
+ </a></span></dt><dt><span class="section"><a
href="jpa_2.2.html#jpa_2.2_UseNativeSequenceCache">2.1.4.
+ useNativeSequenceCache Property.
+ </a></span></dt><dt><span class="section"><a
href="jpa_2.2.html#jpa_2.2_cascadePersist">2.1.5.
+ Cascade persist behavior
+ </a></span></dt><dt><span class="section"><a
href="jpa_2.2.html#jpa_2.2_LifecycleEventManager">2.1.6.
+ Life Cycle Event Manager Callback Behavior
+ </a></span></dt><dt><span class="section"><a
href="jpa_2.2.html#jpa_2.2_sharedCacheMode">2.1.7.
+ shared-cache-mode Property
+ </a></span></dt></dl></dd></dl></div>
+
+ <div class="section" id="jpa_2.2_incompatibilities"><div
class="titlepage"><div><div><h3
class="title">2.1. Incompatibilities</h3></div></div></div><div
class="toc"><dl class="toc"><dt><span class="section"><a
href="jpa_2.2.html#jpa_2.2_allocationSize">2.1.1.
+ allocationSize Property of Sequence Generator
+ </a></span></dt><dt><span class="section"><a
href="jpa_2.2.html#jpa_2.2_metamodelArrays">2.1.2.
+ MetaModel Attributes for Arrays
+ </a></span></dt><dt><span class="section"><a
href="jpa_2.2.html#jpa_2.2_SupportsSetClob">2.1.3.
+ supportsSetClob Property.
+ </a></span></dt><dt><span class="section"><a
href="jpa_2.2.html#jpa_2.2_UseNativeSequenceCache">2.1.4.
+ useNativeSequenceCache Property.
+ </a></span></dt><dt><span class="section"><a
href="jpa_2.2.html#jpa_2.2_cascadePersist">2.1.5.
+ Cascade persist behavior
+ </a></span></dt><dt><span class="section"><a
href="jpa_2.2.html#jpa_2.2_LifecycleEventManager">2.1.6.
+ Life Cycle Event Manager Callback Behavior
+ </a></span></dt><dt><span class="section"><a
href="jpa_2.2.html#jpa_2.2_sharedCacheMode">2.1.7.
+ shared-cache-mode Property
+ </a></span></dt></dl></div>
+
+ <p>
+ The following sections indicate changes that are incompatible
+ between OpenJPA 2.1.x releases and the 2.2.0 release.
+ </p>
+ <div class="section" id="jpa_2.2_allocationSize"><div
class="titlepage"><div><div><h4 class="title">2.1.1.
+ allocationSize Property of Sequence Generator
+ </h4></div></div></div>
+
+
+ <p>
+ In previous releases, specifying the <code
class="literal">allocationSize</code> property of
+ <a class="link"
href="jpa_overview_mapping_sequence.html#jpa_overview_mapping_sequence_seqgen"
title="5.1. Sequence Generator">sequence generator</a>
+ affected only sequence definition in the database. During
+ schema creation, the <code class="literal">INCREMENT
BY</code> clause of
+ <code class="literal">CREATE SEQUENCE</code> statement
always
+ had a value of 1 and on DB2, Oracle and PostgreSQL
databases a <code class="literal">CACHE</code> clause
+ was added with the value of <code
class="literal">allocationSize</code> property. Such a statement caused
+ sequence values being cached in the database. Starting
with OpenJPA 2.2.0,
+ sequence values are cached in the jvm memory and the <code
class="literal">allocationSize</code>
+ property determines size of that cache. The <code
class="literal">CACHE</code> clause is no longer used,
+ instead the <code class="literal">INCREMENT BY</code>
clause gets its value equal to the
+ <code class="literal">allocationSize</code> property. Such
a strategy reduces the number of database roundtrips
+ required for retrieving sequence values considerably.
+ </p>
+ <p>
+ In order for the existing applications to work with OpenJPA
+ 2.2.0, you have to manually recreate or redefine
sequences, specifying
+ the correct <code class="literal">INCREMENT BY</code>
value and, possibly, correct initial sequence value.
+ Note that the default value of the <code
class="literal">allocationSize</code> property is 50 and that
+ value is used if the property is not specified.
+ </p>
+ <p>
+ The requirement for sequence modification applies to all
databases that support sequences, regardless of
+ the <code class="literal">CACHE</code> clause being
supported. The only exception is Firebird database -
+ since with this database the increment step is determined
during sequence
+ value fetch, no migration activity is needed.
+ </p>
+ <p>
+ To maintain the old behavior of sequence generator in
OpenJPA 2.2.0, you can:
+ </p><div class="itemizedlist"><ul class="itemizedlist"
style="list-style-type: disc; "><li class="listitem">
+ <p>
+ Set the <code
class="literal">allocationSize</code> property value to 1.
+ </p>
+ </li><li class="listitem">
+ <p>
+ Additionally, if the <code
class="literal">CACHE</code> clause has to be emitted in sequence definition,
+ this can be accomplished by overriding the
+ <a class="ulink"
href="../javadoc/org/apache/openjpa/jdbc/sql/DBDictionary.html#getCreateSequenceSQL(org.apache.openjpa.jdbc.schema.Sequence)"
target="_top">
+ <code
class="methodname">DBDictionary.getCreateSequenceSQL</code></a> method.
+ </p>
+ </li></ul></div><p>
+ </p>
+ </div>
+ <div class="section" id="jpa_2.2_metamodelArrays"><div
class="titlepage"><div><div><h4 class="title">2.1.2.
+ MetaModel Attributes for Arrays
+ </h4></div></div></div>
+
+
+ <p>
+ In previous releases OpenJPA's MetaModel implementation
generated a ListAttribute for every array. This behavior is correct if the
array
+ is annotated as a PersistentCollection, but not correct
for un-annotated arrays (e.g. byte[], char[]). In OpenJPA 2.2.0 this behavior
was corrected
+ so that arrays which are not stored as
PersistentCollections will use a SingularAttribute instead of a ListAttribute.
+ </p>
+ <p>
+ If your application uses the MetaModel API and your
entities contain arrays of any of the following types: byte[], Byte[], char[],
Character[] and
+ do not use the @PersistentCollection annotation with those
fields you will need to update your application to use OpenJPA 2.2.0.
+ </p>
+ <p> In order for the existing applications to work with
OpenJPA you may:
+ </p><div class="itemizedlist"><ul class="itemizedlist"
style="list-style-type: disc; "><li class="listitem">
+ <p> Regenerate the canonical metamodel classes</p>
+ </li><li class="listitem">
+ <p> Set the Compatibility property <code
class="literal">UseListAttributeForArrays</code> to <code
class="literal">true</code> in persistence.xml
+ </p><pre class="programlisting"> <property
name="openjpa.Compatibility"
value="UseListAttributeForArrays=true"/></pre><p>
+ </p>
+ </li></ul></div><p>
+ </p>
+ </div>
+ <div class="section" id="jpa_2.2_SupportsSetClob"><div
class="titlepage"><div><div><h4 class="title">2.1.3.
+ supportsSetClob Property.
+ </h4></div></div></div>
+
+
+ <p>
+ In OpenJPA 2.2.0, code was added to allow the setting of
CLOB or XML data larger than 4000 bytes. This functionality
+ was eventually back ported to previous releases, and
enabled by the <code class="literal">supportsSetClob</code> property on the
OracleDictionary. Setting this property
+ has no effect in 2.2.0 and later releases and any
occurrence of it should be removed.
+ </p>
+ </div>
+ <div class="section" id="jpa_2.2_UseNativeSequenceCache"><div
class="titlepage"><div><div><h4 class="title">2.1.4.
+ useNativeSequenceCache Property.
+ </h4></div></div></div>
+
+
+ <p>
+ In OpenJPA 2.2.0, code was added which changed the way
sequences were generated, please see
+ <a class="xref" href="jpa_2.2.html#jpa_2.2_allocationSize"
title="2.1.1. allocationSize Property of Sequence
Generator">Section 2.1.1, “
+ allocationSize Property of Sequence Generator
+ ”</a> for details. This functionality was eventually
back ported
+ to previous releases, and enabled by the <code
class="literal">useNativeSequenceCache</code> property on the DBDictionary.
Setting this property
+ has no effect in 2.2.0 and later releases and any
occurrence of it should be removed. If previous behavior is
+ desired (i.e. <code
class="literal">useNativeSequenceCache=true</code>), please see the details
described in section
+ <a class="xref" href="jpa_2.2.html#jpa_2.2_allocationSize"
title="2.1.1. allocationSize Property of Sequence
Generator">Section 2.1.1, “
+ allocationSize Property of Sequence Generator
+ ”</a>.
+ </p>
+ </div>
+ <div class="section" id="jpa_2.2_cascadePersist"><div
class="titlepage"><div><div><h4 class="title">2.1.5.
+ Cascade persist behavior
+ </h4></div></div></div>
+
+
+ <p>
+ In previous releases, OpenJPA would
check the database for the
+ existence of the related Entity before
persisting the relationship to
+ that Entity. This resulted in an extra
Select being sent to the
+ database. In 2.2.0, code was added so
that when cascading a persist to
+ a related Entity without persistence
state, the persist (insert) will
+ happen without first checking the
database. This may result in an
+ EntityExistsException if the related
Entity already exists in the
+ database. To revert this behavior to
the previous release, set the
+ value of the <code
class="literal">openjpa.Compatibility</code>
+ property <code
class="literal">CheckDatabaseForCascadePersistToDetachedEntity</code>
+ to <code class="literal">true</code>.
+ </p>
+ </div>
+ <div class="section" id="jpa_2.2_LifecycleEventManager"><div
class="titlepage"><div><div><h4 class="title">2.1.6.
+ Life Cycle Event Manager Callback Behavior
+ </h4></div></div></div>
+
+
+ <p>
+ Life cycle event manager is used to manage entity's life
cycle event callback.
+ In previous releases, Life cycle event manager is scoped
to EntityManagerFactory.
+ This means listeners registered to an individual
EntityManager may get life cycle
+ event callbacks for entity that it does not manage.
+ </p>
+ <p>
+ From 2.2.1 release, the default callback behavior of the
life cycle event manager
+ is changed to scope to each EntityManager.
+ To revert this behavior to the previous release, set the
+ value of the <code
class="literal">openjpa.Compatibility</code>
+ property <code
class="literal">SingletonLifecycleEventManager</code>
+ to <code class="literal">true</code>.
+ </p>
+ </div>
+ <div class="section" id="jpa_2.2_sharedCacheMode"><div
class="titlepage"><div><div><h4 class="title">2.1.7.
+ shared-cache-mode Property
+ </h4></div></div></div>
+
+
+ <p>
+ In the previous release, when the shared-cache-mode is
enabled and the DataCache property is not set
+ or set to false, there will be no data caching.
+ </p>
+ <p>
+ From 2.2.2 release, the caching will be turned on if the
shared-cache-mode is enabled. Please see the
+ details described in section <a class="xref"
href="ref_guide_caching.html#ref_guide_shared_cache_mode_integration"
title="1.1.2. Integration with JPA standard shared cache
mode">Section 1.1.2, “
+ Integration with JPA standard shared cache mode
+ ”</a>.
+ </p>
+ </div>
+ </div>
+ </div><div class="navfooter"><hr><table width="100%" summary="Navigation
footer"><tr><td width="40%" align="left"><a accesskey="p"
href="migration_considerations.html">Prev</a> </td><td width="20%"
align="center"><a accesskey="u"
href="migration_considerations.html">Up</a></td><td width="40%"
align="right"> <a accesskey="n"
href="jpa_2.3.html">Next</a></td></tr><tr><td width="40%" align="left"
valign="top">Appendix 3.
+ Migration Considerations
+ </td><td width="20%" align="center"><a accesskey="h"
href="manual.html">Home</a></td><td width="40%" align="right"
valign="top"> 3.
+ OpenJPA 2.3.0
+ </td></tr></table></div></body></html>
\ No newline at end of file
Added:
websites/production/openjpa/content/builds/2.4.2/apache-openjpa/docs/jpa_2.3.html
==============================================================================
---
websites/production/openjpa/content/builds/2.4.2/apache-openjpa/docs/jpa_2.3.html
(added)
+++
websites/production/openjpa/content/builds/2.4.2/apache-openjpa/docs/jpa_2.3.html
Fri Jan 6 19:19:20 2017
@@ -0,0 +1,85 @@
+<html><head>
+ <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+ <title>3. OpenJPA 2.3.0</title><base href="display"><link
rel="stylesheet" type="text/css" href="css/docbook.css"><meta name="generator"
content="DocBook XSL Stylesheets V1.79.1"><link rel="home" href="manual.html"
title="Apache OpenJPA 2.4 User's Guide"><link rel="up"
href="migration_considerations.html" title="Appendix 3. Migration
Considerations"><link rel="prev" href="jpa_2.2.html" title="2. OpenJPA
2.2.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084"
alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation
header"><tr><th colspan="3" align="center">3.
+ OpenJPA 2.3.0
+ </th></tr><tr><td width="20%" align="left"><a accesskey="p"
href="jpa_2.2.html">Prev</a> </td><th width="60%"
align="center">Appendix 3.
+ Migration Considerations
+ </th><td width="20%" align="right"> </td></tr></table><hr></div><div
class="section" id="jpa_2.3"><div class="titlepage"><div><div><h2 class="title"
style="clear: both">3.
+ OpenJPA 2.3.0
+ </h2></div></div></div><div class="toc"><dl class="toc"><dt><span
class="section"><a href="jpa_2.3.html#jpa_2.3_incompatibilities">3.1.
Incompatibilities</a></span></dt><dd><dl><dt><span class="section"><a
href="jpa_2.3.html#jpa_2.3_MappingTool">3.1.1.
+ MappingTool Behavior for DB2 and Derby
+ </a></span></dt><dt><span class="section"><a
href="jpa_2.3.html#jpa_2.3_RequiresSearchStringEscapeForLike">3.1.2.
+ RequiresSearchStringEscapeForLike DBDictionary Property
+ </a></span></dt><dt><span class="section"><a
href="jpa_2.3.html#ReturnNullOnEmptyAggregateResult">3.1.3.
+ Return value of aggregate functions in SELECT clause
+ </a></span></dt></dl></dd></dl></div>
+
+ <div class="section" id="jpa_2.3_incompatibilities"><div
class="titlepage"><div><div><h3
class="title">3.1. Incompatibilities</h3></div></div></div><div
class="toc"><dl class="toc"><dt><span class="section"><a
href="jpa_2.3.html#jpa_2.3_MappingTool">3.1.1.
+ MappingTool Behavior for DB2 and Derby
+ </a></span></dt><dt><span class="section"><a
href="jpa_2.3.html#jpa_2.3_RequiresSearchStringEscapeForLike">3.1.2.
+ RequiresSearchStringEscapeForLike DBDictionary Property
+ </a></span></dt><dt><span class="section"><a
href="jpa_2.3.html#ReturnNullOnEmptyAggregateResult">3.1.3.
+ Return value of aggregate functions in SELECT clause
+ </a></span></dt></dl></div>
+
+ <p>
+ The following sections indicate changes that are incompatible
+ between OpenJPA 2.2.x releases and the 2.3.0 release.
+ </p>
+ <div class="section" id="jpa_2.3_MappingTool"><div
class="titlepage"><div><div><h4 class="title">3.1.1.
+ MappingTool Behavior for DB2 and Derby
+ </h4></div></div></div>
+
+ <p>
+ In previous releases, the MappingTool mapped <code
class="literal">java.math.BigDecimal</code> fields to the database type
+ DOUBLE, and as such, ignored <code
class="literal">column</code> and <code class="literal">precision</code> values
that might have been specified via the
+ <code class="literal">javax.persistence.Column</code>
annotation.
+ </p>
+ <p>
+ From the 2.3.0 release, <code
class="literal">java.math.BigDecimal</code> fields are now mapped to the
database type DECIMAL
+ and it is very likely that you will need to specify <code
class="literal">column</code> and <code class="literal">precision</code> via
+ the <code class="literal">javax.persistence.Column</code>
annotation.
+ </p>
+ </div>
+ <div class="section"
id="jpa_2.3_RequiresSearchStringEscapeForLike"><div
class="titlepage"><div><div><h4 class="title">3.1.2.
+ RequiresSearchStringEscapeForLike DBDictionary Property
+ </h4></div></div></div>
+
+
+ <p>
+ In previous releases, the default value for the property
RequiresSearchStringEscapeForLike is true and caused the
+ unexpected escape clause appended to the SQL statement.
+ For example, user created a named query like this:
+ </p><pre class="programlisting"> SELECT o.computerName
FROM CompUser o WHERE o.name LIKE ?</pre><p>
+ At run time the following query is generated:
+ </p><pre class="programlisting"> SELECT t0.computerName
FROM CompUser t0 WHERE (t0.name LIKE ? ESCAPE '\')</pre><p>
+ ESCAPE '\' shouldn't be appended to the query.
+ </p>
+ <p>
+ From the 2.3.0 release, RequiresSearchStringEscapeForLike
property is set to false by default. You can configure
+ RequiresSearchStringEscapeForLike property to be true if
the old behavior is desired.
+ </p>
+ </div>
+ <div class="section" id="ReturnNullOnEmptyAggregateResult"><div
class="titlepage"><div><div><h4 class="title">3.1.3.
+ Return value of aggregate functions in SELECT clause
+ </h4></div></div></div>
+
+
+ <p>
+ The JPA specification states "If SUM, AVG, MAX, or MIN is
used, and there are no values to which the aggregate function can be
+ applied, the result of the aggregate function is NULL."
Prior to this update, OpenJPA incorrectly returned 0 for SUM, AVG, MIN,
+ and MAX when a state field being aggregated is numeric.
This behavior affects both JPQL and Criteria queries. With this update,
+ OpenJPA will return a null result value for these
aggregate functions when a query returns no result.
+ </p>
+ <p>
+ To re-enable the prior behavior, you need to set the
following persistence property in your persistence.xml or when
+ creating an EntityManagerFactory.
+ </p><pre class="programlisting">
+ <property name="openjpa.Compatibility"
value="ReturnNullOnAggregateResult=false"/>
+ </pre><p>
+ </p>
+ </div>
+ </div>
+ </div><div class="navfooter"><hr><table width="100%" summary="Navigation
footer"><tr><td width="40%" align="left"><a accesskey="p"
href="jpa_2.2.html">Prev</a> </td><td width="20%" align="center"><a
accesskey="u" href="migration_considerations.html">Up</a></td><td width="40%"
align="right"> </td></tr><tr><td width="40%" align="left"
valign="top">2.
+ OpenJPA 2.2.0
+ </td><td width="20%" align="center"><a accesskey="h"
href="manual.html">Home</a></td><td width="40%" align="right"
valign="top"> </td></tr></table></div></body></html>
\ No newline at end of file
