Added:
websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/dbsupport_sybase.html
==============================================================================
---
websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/dbsupport_sybase.html
(added)
+++
websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/dbsupport_sybase.html
Wed May 14 22:22:23 2014
@@ -0,0 +1,71 @@
+<html><head>
+ <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+ <title>24. Sybase Adaptive Server</title><base href="display"><link
rel="stylesheet" type="text/css" href="css/docbook.css"><meta name="generator"
content="DocBook XSL-NS Stylesheets V1.76.1"><link rel="home"
href="manual.html" title="Apache OpenJPA 2.3 User's Guide"><link rel="up"
href="supported_databases.html" title="Appendix 2. Supported
Databases"><link rel="prev" href="dbsupport_soliddb.html" title="23. IBM
solidDB"><link rel="next" href="migration_considerations.html"
title="Appendix 3. Migration Considerations"></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">24.
+ Sybase Adaptive Server
+ </th></tr><tr><td width="20%" align="left"><a accesskey="p"
href="dbsupport_soliddb.html">Prev</a> </td><th width="60%"
align="center">Appendix 2.
+ Supported Databases
+ </th><td width="20%" align="right"> <a accesskey="n"
href="migration_considerations.html">Next</a></td></tr></table><hr></div><div
class="section" title="24. Sybase Adaptive Server"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"
id="dbsupport_sybase">24.
+ Sybase Adaptive Server
+ </h2></div></div></div><div class="toc"><dl><dt><span
class="section"><a href="dbsupport_sybase.html#dbsupport_sybase_issues">24.1.
+ Known issues with Sybase
+ </a></span></dt></dl></div>
+
+ <div class="example"><a name="example_props_sybase"></a><p
class="title"><b>Example 2.24.
+ Example properties for Sybase
+ </b></p><div class="example-contents">
+
+<pre class="programlisting">
+openjpa.ConnectionDriverName: com.sybase.jdbc2.jdbc.SybDriver
+openjpa.ConnectionURL: \
+
jdbc:sybase:Tds:SERVER_NAME:4100/DB_NAME?ServiceName=DB_NAME&BE_AS_JDBC_COMPLIANT_AS_POSSIBLE=true
+</pre>
+ </div></div><br class="example-break">
+ <div class="section" title="24.1. Known issues with Sybase"><div
class="titlepage"><div><div><h3 class="title"
id="dbsupport_sybase_issues">24.1.
+ Known issues with Sybase
+ </h3></div></div></div>
+
+ <div class="itemizedlist"><ul class="itemizedlist" type="disc"><li
class="listitem">
+ <p>
+The "<code class="literal">DYNAMIC_PREPARE</code>" parameter of the Sybase
JDBC driver
+cannot be used with OpenJPA.
+ </p>
+ </li><li class="listitem">
+ <p>
+Datastore locking cannot be used when manipulating many-to-many relations using
+the default OpenJPA schema created by the schematool, unless an auto-increment
+primary key field is manually added to the table.
+ </p>
+ </li><li class="listitem">
+ <p>
+Persisting a zero-length string results in a string with a single space
+character being returned from Sybase, Inc.'s JDBC driver.
+ </p>
+ </li><li class="listitem">
+ <p>
+The <code class="literal">BE_AS_JDBC_COMPLIANT_AS_POSSIBLE</code> is required
in order to
+use datastore (pessimistic) locking. Failure to set this property may lead to
+obscure errors like " <code class="literal">FOR UPDATE can not be used in a
SELECT which is
+not part of the declaration of a cursor or which is not inside a stored
+procedure.</code> ".
+ </p>
+ </li><li class="listitem">
+ <p>
+Applications performing update/insert data of the BigDecimal Java type may
fail
+with OptimisticException if the data exceeds the scale or precision of the
+column on Sybase. To avoid this problem, applications can specify the precision
+and scale for the numeric type by setting numericTypeName='NUMERIC(p,s)' for
+the column type mapped by the BigDecimal Java type. See
+<a class="link" href="ref_guide_conf_jdbc.html#openjpa.jdbc.DBDictionary"
title="6.2. openjpa.jdbc.DBDictionary">openjpa.jdbc.DBDictionary</a> for
+more detail. Alternatively, application can set the precision and scale using
+the standard <code class="classname">Column</code> annotation, described in
+<a class="xref" href="jpa_overview_mapping_column.html" title="3.
Column">Section 3, “
+ Column
+ ”</a>.
+ </p>
+ </li></ul></div>
+ </div>
+ </div><div class="navfooter"><hr><table width="100%" summary="Navigation
footer"><tr><td width="40%" align="left"><a accesskey="p"
href="dbsupport_soliddb.html">Prev</a> </td><td width="20%"
align="center"><a accesskey="u" href="supported_databases.html">Up</a></td><td
width="40%" align="right"> <a accesskey="n"
href="migration_considerations.html">Next</a></td></tr><tr><td width="40%"
align="left" valign="top">23.
+ IBM solidDB
+ </td><td width="20%" align="center"><a accesskey="h"
href="manual.html">Home</a></td><td width="40%" align="right"
valign="top"> Appendix 3.
+ Migration Considerations
+ </td></tr></table></div></body></html>
\ No newline at end of file
Propchange:
websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/dbsupport_sybase.html
------------------------------------------------------------------------------
svn:mime-type = text/plain
Added:
websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/dbunverified.html
==============================================================================
---
websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/dbunverified.html
(added)
+++
websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/dbunverified.html
Wed May 14 22:22:23 2014
@@ -0,0 +1,46 @@
+<html><head>
+ <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+ <title>4. Unverified Database Matrix</title><base
href="display"><link rel="stylesheet" type="text/css"
href="css/docbook.css"><meta name="generator" content="DocBook XSL-NS
Stylesheets V1.76.1"><link rel="home" href="manual.html" title="Apache OpenJPA
2.3 User's Guide"><link rel="up" href="supported_databases.html"
title="Appendix 2. Supported Databases"><link rel="prev"
href="dbcompatible.html" title="3. Compatible Database Matrix"><link
rel="next" href="dbsupport_derby.html" title="5. Apache
Derby"></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">4.
+ Unverified Database Matrix
+ </th></tr><tr><td width="20%" align="left"><a accesskey="p"
href="dbcompatible.html">Prev</a> </td><th width="60%"
align="center">Appendix 2.
+ Supported Databases
+ </th><td width="20%" align="right"> <a accesskey="n"
href="dbsupport_derby.html">Next</a></td></tr></table><hr></div><div
class="section" title="4. Unverified Database Matrix"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"
id="dbunverified">4.
+ Unverified Database Matrix
+ </h2></div></div></div>
+
+ <p>
+Following is a table of the database and JDBC driver versions that have been
reported
+to work with OpenJPA by the community but have not been verified by the
development
+team. In some cases this is a question of availability since the developers
may not
+be able to obtain a license to test, or have experience configuring these
databases.
+For the list of databases that have been fully tested against this release,
please
+refer to the <a class="link" href="dbsupport.html" title="2. Verified
Database Matrix">Verified Database Matrix</a> section.
+ </p>
+ <div class="table"><a name="d5e17726"></a><p
class="title"><b>Table 2.3.
+ Unverified Databases and JDBC Drivers
+ </b></p><div class="table-contents">
+
+ <table summary="
 Unverified Databases and JDBC
Drivers
 " border="1"><colgroup><col align="left"
class="dbname"><col align="left" class="dbversion"><col align="left"
class="drivname"><col align="left"
class="drivversion"></colgroup><thead><tr><th align="left">
+ Database Name
+ </th><th align="left">
+ Database Version
+ </th><th align="left">
+ JDBC Driver Name
+ </th><th align="left">
+ JDBC Driver Version
+ </th></tr></thead><tbody><tr><td align="left">
+ SAP MaxDB
+ </td><td align="left">
+
+ </td><td align="left">
+
+ </td><td align="left">
+
+ </td></tr></tbody></table>
+ </div></div><br class="table-break">
+
+ </div><div class="navfooter"><hr><table width="100%" summary="Navigation
footer"><tr><td width="40%" align="left"><a accesskey="p"
href="dbcompatible.html">Prev</a> </td><td width="20%" align="center"><a
accesskey="u" href="supported_databases.html">Up</a></td><td width="40%"
align="right"> <a accesskey="n"
href="dbsupport_derby.html">Next</a></td></tr><tr><td width="40%" align="left"
valign="top">3.
+ Compatible Database Matrix
+ </td><td width="20%" align="center"><a accesskey="h"
href="manual.html">Home</a></td><td width="40%" align="right"
valign="top"> 5.
+ Apache Derby
+ </td></tr></table></div></body></html>
\ No newline at end of file
Propchange:
websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/dbunverified.html
------------------------------------------------------------------------------
svn:mime-type = text/plain
Added:
websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/features_and_limitations.html
==============================================================================
---
websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/features_and_limitations.html
(added)
+++
websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/features_and_limitations.html
Wed May 14 22:22:23 2014
@@ -0,0 +1,259 @@
+<html><head>
+ <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+ <title>2. Salient Features</title><base href="display"><link
rel="stylesheet" type="text/css" href="css/docbook.css"><meta name="generator"
content="DocBook XSL-NS Stylesheets V1.76.1"><link rel="home"
href="manual.html" title="Apache OpenJPA 2.3 User's Guide"><link rel="up"
href="ref_guide_slice.html" title="Chapter 13. Slice: Distributed
Persistence"><link rel="prev" href="ref_guide_slice.html"
title="Chapter 13. Slice: Distributed Persistence"><link rel="next"
href="slice_configuration.html" title="3. Usage"></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. Salient
Features</th></tr><tr><td width="20%" align="left"><a accesskey="p"
href="ref_guide_slice.html">Prev</a> </td><th width="60%"
align="center">Chapter 13.
+ Slice: Distributed Persistence
+ </th><td width="20%" align="right"> <a accesskey="n"
href="slice_configuration.html">Next</a></td></tr></table><hr></div><div
class="section" title="2. Salient Features"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"
id="features_and_limitations">2. Salient
Features</h2></div></div></div><div class="toc"><dl><dt><span
class="section"><a href="features_and_limitations.html#d5e16758">2.1.
Transparency</a></span></dt><dt><span class="section"><a
href="features_and_limitations.html#d5e16764">2.2.
Scaling</a></span></dt><dt><span class="section"><a
href="features_and_limitations.html#d5e16770">2.3. Distributed
Query</a></span></dt><dt><span class="section"><a
href="features_and_limitations.html#d5e16793">2.4. Data
Distribution</a></span></dt><dt><span class="section"><a
href="features_and_limitations.html#d5e16812">2.5. Data
Replication</a></span></dt><dt><span class="section"><a
href="features_and_limitations.html#d5e16821">2.6. Heterogeneous Dat
abase</a></span></dt><dt><span class="section"><a
href="features_and_limitations.html#d5e16824">2.7. Distributed
Transaction</a></span></dt><dt><span class="section"><a
href="features_and_limitations.html#collocation_constraint">2.8. Collocation
Constraint</a></span></dt></dl></div>
+
+ <div class="section" title="2.1. Transparency"><div
class="titlepage"><div><div><h3 class="title"
id="d5e16758">2.1. Transparency</h3></div></div></div>
+ <p>
+ The primary design objective for Slice is to make the
user
+ application transparent to the change in storage
strategy where
+ data resides in multiple (possibly heterogeneous)
databases instead
+ of a single database. Slice achieves this
transparency by
+ virtualization of multiple databases as a single
database such
+ that OpenJPA object management kernel continues to
interact in
+ exactly the same manner with storage layer.
Similarly,
+ the existing application or the persistent domain model requires
+ <span class="emphasis"><em>no change</em></span> to upgrade from
a single database
+ to a distributed database environment.
+ </p>
+ <p>
+ An existing application developed for a single
database can be
+ adapted to work with multiple databases purely by
configuring
+ a persistence unit via <code
class="classname">META-INF/persistence.xml</code>.
+ </p>
+ </div>
+
+ <div class="section" title="2.2. Scaling"><div
class="titlepage"><div><div><h3 class="title"
id="d5e16764">2.2. Scaling</h3></div></div></div>
+ <p>
+ The primary performance characteristics for Slice is to
scale against
+ growing data volume by <span
class="emphasis"><em>horizontal</em></span> partitioning data
+ across many databases.
+ </p>
+ <p>
+ Slice executes the database operations such as query or
flush <span class="emphasis"><em>in
+ parallel</em></span> across each physical database.
Hence, scaling characteristics
+ against data volume are bound by the size of the
maximum data
+ partition instead of the size of the entire data set.
The use cases
+ where the data is naturally amenable to horizontal
partitions,
+ for example, by temporal interval (e.g. Purchase Orders
per month)
+ or by geographical regions (e.g. Customer by Zip Code)
can derive
+ significant performance benefit and favorable scaling
behavior by
+ using Slice.
+ </p>
+ </div>
+
+ <div class="section" title="2.3. Distributed Query"><div
class="titlepage"><div><div><h3 class="title"
id="d5e16770">2.3. Distributed Query</h3></div></div></div>
+ <p>
+ The queries are executed in parallel across one or more slices and
the
+ individual query results are merged into a single list
before being
+ returned to the caller application. The <span
class="emphasis"><em>merge</em></span> operation is
+ more complex for the queries that involve sorting
and/or specify a
+ range. Slice supports both sorting and range queries.
+ </p>
+ <p>
+ Slice also supports aggregate queries where the aggregate
operation
+ is <span class="emphasis"><em>commutative</em></span>
to partitioning such as
+ <code class="classname">COUNT()</code> or <code
class="classname">MAX()</code> but not <code class="classname">AVG()</code>.
+ </p>
+
+ <p>
+ By default, any query is executed against all available slices.
+ However, the application can target the query only to a
subset of
+ slices by setting <span
class="emphasis"><em>hint</em></span> on <code
class="classname">javax.persistence.Query</code>.
+ The hint key is <code
class="classname">openjpa.hint.slice.Target</code> and
+ hint value is an array of slice identifiers. The following
+ example shows how to target a query only to a pair of slices
+ with logical identifier <code
class="classname">"One"</code> and <code class="classname">"Two"</code>.
+
+ </p><pre class="programlisting">
+ EntityManager em = ...;
+ em.getTransaction().begin();
+ String hint = "openjpa.hint.slice.Target";
+ Query query = em.createQuery("SELECT p FROM PObject")
+ .setHint(hint, new
String[]{"One", "Two"});
+ List result = query.getResultList();
+ // verify that each instance is originating from the hinted
slices
+ for (Object pc : result) {
+ String sliceOrigin = SlicePersistence.getSlice(pc);
+ assertTrue ("One".equals(sliceOrigin) ||
"Two".equals(sliceOrigin));
+ }
+
+ </pre><p>
+ </p>
+
+ <p>
+ To confine queries to a subset of slices via setting query hints
can be considered
+ intrusive to existing application. The alternative means of
targeting queries is to
+ configure a <span class="emphasis"><em>Query Target
Policy</em></span>. This policy is configured
+ via plug-in property <code
class="classname">openjpa.slice.QueryTargetPolicy</code>. The
+ plug-in property is fully-qualified class name of an implementation
+ for <code
class="classname">org.apache.openjpa.slice.QueryTargetPolicy</code> interface.
+ This interface contract allows a user application to target a
query to a subset
+ of slices based on the query and its bound parameters. The query
target policy is consulted
+ only when no explicit target hint is set on the query. By default,
the policy
+ executes a query on all available slices.
+ </p>
+
+ <p>
+ A similar policy interface <code
class="classname">org.apache.openjpa.slice.FinderTargetPolicy</code>
+ is available to target queries that originate from <code
class="classname">find()</code>
+ by primary key. This finder target policy is consulted
+ only when no explicit target hint is set on the current fetch
plan. By default, the policy
+ executes a query on all available slices to find an instance by
its primary key.
+ </p>
+ </div>
+
+ <div class="section" title="2.4. Data Distribution"><div
class="titlepage"><div><div><h3 class="title" id="d5e16793">2.4. Data
Distribution</h3></div></div></div>
+ <p>
+ The user application decides how the newly persistent instances
be
+ distributed across the slices. The user application specifies the
+ data distribution policy by implementing
+ <code
class="classname">org.apache.openjpa.slice.DistributionPolicy</code>.
+
+ The <code class="classname">DistributionPolicy</code>
interface
+ is simple with a single method. The complete listing
of the
+ documented interface follows:
+ </p><pre class="programlisting">
+
+ public interface DistributionPolicy {
+ /**
+ * Gets the name of the slice where the given newly
persistent
+ * instance will be stored.
+ *
+ * @param pc The newly persistent or to-be-merged
object.
+ * @param slices name of the configured slices.
+ * @param context persistence context managing the
given instance.
+ *
+ * @return identifier of the slice. This name must
match one of the
+ * configured slice names.
+ * @see DistributedConfiguration#getSliceNames()
+ */
+ String distribute(Object pc, List<String> slices,
Object context);
+ }
+
+ </pre><p>
+ </p>
+
+ <p>
+ Slice runtime invokes this user-supplied method for
the newly
+ persistent instance that is explicit argument of the
+ <code
class="classname">javax.persistence.EntityManager.persist(Object pc)</code>
+ method. The user application must return a valid slice
name from
+ this method to designate the target slice for the
given instance.
+ The data distribution policy may be based on the
attribute
+ of the data itself. For example, all Customer whose
first name
+ begins with character 'A' to 'M' will be stored in one
slice
+ while names beginning with 'N' to 'Z' will be stored
in another
+ slice. The noteworthy aspect of such policy
implementation is
+ the attribute values that participate in
+ the distribution policy logic should be set before
invoking
+ <code class="classname">EntityManager.persist()</code>
method.
+ </p>
+
+ <p>
+ The user application needs to specify the target slice
<span class="emphasis"><em>only</em></span>
+ for the <span class="emphasis"><em>root</em></span>
instance i.e. the explicit argument for the
+ <code class="classname">EntityManager.persist(Object
pc)</code> method. Slice computes
+ the transitive closure of the graph i.e. the set of all
instances
+ directly or indirectly reachable from the root instance
and stores
+ them in the same target slice.
+ </p>
+
+ <p>
+ Slice tracks the original database for existing instances. When
+ an application issues a query, the resultant instances can be
loaded
+ from different slices. As Slice tracks the original slice for
each
+ instance, any subsequent update to an instance is committed to
the
+ appropriate original database slice.
+ </p>
+
+ <div class="note" title="Note" style="margin-left: 0.5in;
margin-right: 0.5in;"><h3 class="title">Note</h3>
+ <p>
+ You can find the original slice of an instance <code
class="classname">pc</code> by
+ the static utility method
+ <code class="methodname">SlicePersistence.getSlice(pc)</code>.
+ This method returns the slice identifier associated with the
+ given <span class="emphasis"><em>managed</em></span> instance. If
the instance is not
+ being managed then the method return null because any unmanaged or
+ detached instance is not associated with any slice.
+ </p>
+ </div>
+ </div>
+
+ <div class="section" title="2.5. Data Replication"><div
class="titlepage"><div><div><h3 class="title" id="d5e16812">2.5. Data
Replication</h3></div></div></div>
+ <p>
+ While Slice ensures that the transitive closure is
stored in the
+ same slice, there can be data elements that are
commonly referred by
+ many instances such as Country or Currency code. Such
quasi-static
+ master data can be stored as identical copies in
multiple slices.
+ The user application must enumerate the replicated
entity type names in
+ <code
class="classname">openjpa.slice.ReplicatedTypes</code> as a comma-separated list
+ and implement a <code
class="classname">org.apache.openjpa.slice.ReplicationPolicy</code>
+ interface. The <code
class="classname">ReplicationPolicy</code> interface
+ is quite similar to <code
class="classname">DistributionPolicy</code>
+ interface except it returns an array of target slice
names instead
+ of a single slice.
+ </p><pre class="programlisting">
+
+ String[] replicate(Object pc, List<String>
slices, Object context);
+
+ </pre><p>
+ </p>
+ <p>
+ The default implementation assumes that
replicated instances are
+ stored in all available slices. If any such
replicated instance
+ is modified then the modification is updated to
all target slices
+ to maintain the critical assumption that the
state of a replicated
+ instance is identical across all its target
slices.
+ </p>
+ </div>
+
+ <div class="section" title="2.6. Heterogeneous Database"><div
class="titlepage"><div><div><h3 class="title"
id="d5e16821">2.6. Heterogeneous Database</h3></div></div></div>
+ <p>
+ Each slice can be configured independently with its own JDBC
+ driver and other connection parameters. Hence the target
database
+ environment can constitute of heterogeneous databases.
+ </p>
+ </div>
+
+ <div class="section" title="2.7. Distributed Transaction"><div
class="titlepage"><div><div><h3 class="title"
id="d5e16824">2.7. Distributed Transaction</h3></div></div></div>
+ <p>
+ The database slices participate in a global transaction provided
+ each slice is configured with a XA-compliant JDBC driver, even
+ when the persistence unit is configured for <code
class="classname">RESOURCE_LOCAL</code>
+ transaction.
+ </p>
+ <p>
+ </p><div class="warning" title="Warning" style="margin-left:
0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3>
+ If any of the configured slices is not XA-compliant <span
class="emphasis"><em>and</em></span>
+ the persistence unit is configured for <code
class="classname">RESOURCE_LOCAL</code>
+ transaction then each slice is committed without any two-phase
+ commit protocol. If commit on any slice fails, then atomic nature
of
+ the transaction is not ensured.
+ </div><p>
+ </p>
+ </div>
+
+ <div class="section" title="2.8. Collocation Constraint"><div
class="titlepage"><div><div><h3 class="title"
id="collocation_constraint">2.8. Collocation
Constraint</h3></div></div></div>
+ <p>
+ No relationship can exist across database slices. In O-R mapping
parlance,
+ this condition translates to the limitation that the transitive
closure of an object graph must be
+ <span class="emphasis"><em>collocated</em></span> in the same
database.
+ For example, consider a domain model where Person relates to
Address.
+ Person X refers to Address A while Person Y refers to Address B.
+ Collocation Constraint means that <span
class="emphasis"><em>both</em></span> X and A
+ must be stored in the same
+ database slice. Similarly Y and B must be stored in a single slice.
+ </p>
+ <p>
+ Slice, however, helps to maintain collocation constraint
automatically.
+ The instances in the closure set of any newly persistent instance
+ reachable via cascaded relationship is stored in the same slice.
+ The user-defined distribution policy requires to supply the slice
+ for the root instance only.
+ </p>
+ </div>
+ </div><div class="navfooter"><hr><table width="100%" summary="Navigation
footer"><tr><td width="40%" align="left"><a accesskey="p"
href="ref_guide_slice.html">Prev</a> </td><td width="20%"
align="center"><a accesskey="u" href="ref_guide_slice.html">Up</a></td><td
width="40%" align="right"> <a accesskey="n"
href="slice_configuration.html">Next</a></td></tr><tr><td width="40%"
align="left" valign="top">Chapter 13.
+ Slice: Distributed Persistence
+ </td><td width="20%" align="center"><a accesskey="h"
href="manual.html">Home</a></td><td width="40%" align="right"
valign="top"> 3. Usage</td></tr></table></div></body></html>
\ No newline at end of file
Propchange:
websites/production/openjpa/content/builds/2.3.0/apache-openjpa/docs/features_and_limitations.html
------------------------------------------------------------------------------
svn:mime-type = text/plain
