db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From arm...@apache.org
Subject cvs commit: db-ojb/src/doc/forrest/src/documentation/content/xdocs site.xml
Date Tue, 27 Jul 2004 00:29:31 GMT
arminw      2004/07/26 17:29:31

  Modified:    src/doc/forrest/src/documentation/content/xdocs/docu/guides
                        Tag: OJB_1_0_RELEASE basic-technique.xml
                        connection.xml deployment.xml platforms.xml
               src/doc/forrest/src/documentation/content/xdocs/docu/tutorials
                        Tag: OJB_1_0_RELEASE pb-tutorial.xml
               src/doc/forrest/src/documentation/content/xdocs/docu Tag:
                        OJB_1_0_RELEASE faq.xml getting-started.xml
               src/doc/forrest/src/documentation/content/xdocs Tag:
                        OJB_1_0_RELEASE site.xml
  Log:
  merge changes made since 1.0 from trunk to OJB_1_0_RELEASE branch
  
  Revision  Changes    Path
  No                   revision
  No                   revision
  1.1.2.1   +14 -3     db-ojb/src/doc/forrest/src/documentation/content/xdocs/docu/guides/basic-technique.xml
  
  Index: basic-technique.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/src/doc/forrest/src/documentation/content/xdocs/docu/guides/basic-technique.xml,v
  retrieving revision 1.1
  retrieving revision 1.1.2.1
  diff -u -r1.1 -r1.1.2.1
  --- basic-technique.xml	20 Jun 2004 09:12:33 -0000	1.1
  +++ basic-technique.xml	27 Jul 2004 00:29:31 -0000	1.1.2.1
  @@ -205,7 +205,10 @@
   >
       <foreignkey field-ref="sampleArticleId""/>
   </reference-descriptor>]]></source>
  -
  +            <note>
  +                When using primitive primary key fields, please pay attention on
  +                <link href="site:faq/primitive-null">how OJB manage <code>null</code>
for primitive PK/FK</link>
  +            </note>
   
               <section>
                   <title>1:1 auto-xxx setting</title>
  @@ -439,7 +442,10 @@
                   the repository file. But in some cases the <em>default</em>
behaviour of OJB is undesired.
                   Please <link href="site:advanced-technique/which-collection-type">read
here for more information</link>.
               </p>
  -
  +            <note>
  +                When using primitive primary key fields, please pay attention on
  +                <link href="site:faq/primitive-null">how OJB manage <code>null</code>
for primitive PK/FK</link>
  +            </note>
   
               <section>
                   <title>1:n auto-xxx setting</title>
  @@ -856,7 +862,12 @@
                       <code>Role</code>.
                   </p>
               </section>
  +            <note>
  +                When using primitive primary key fields, please pay attention on
  +                <link href="site:faq/primitive-null">how OJB manage <code>null</code>
for primitive PK/FK</link>
  +            </note>
   
  +            
               <section>
                   <title>m:n auto-xxx setting</title>
                   <p>
  
  
  
  1.1.2.1   +26 -18    db-ojb/src/doc/forrest/src/documentation/content/xdocs/docu/guides/connection.xml
  
  Index: connection.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/src/doc/forrest/src/documentation/content/xdocs/docu/guides/connection.xml,v
  retrieving revision 1.1
  retrieving revision 1.1.2.1
  diff -u -r1.1 -r1.1.2.1
  --- connection.xml	20 Jun 2004 09:12:33 -0000	1.1
  +++ connection.xml	27 Jul 2004 00:29:31 -0000	1.1.2.1
  @@ -212,43 +212,51 @@
                       used
                       <code>PersistenceBroker</code> instance:
                   </p>
  -                <source>
  -PersistenceBroker broker = PersistenceBrokerFactory.
  -createPersistenceBroker(myKey);
  +                <source><![CDATA[
  +PersistenceBroker broker = PersistenceBrokerFactory.createPersistenceBroker(myKey);
   broker.beginTransaction();
   // do something
   
   Connection con = broker.serviceConnectionManager().getConnection();
   // perform your connction action and do more
  +// close the created statement and result set
   
   broker.commitTransaction();
  -broker.close();
  -                </source>
  +broker.close();]]></source>
  +                <p>
  +                    After obtain the connection with
  +                    <code>broker.serviceConnectionManager().getConnection()</code>,
the connection can be used
  +                    in a 'normal' way. The user is responsible for cleanup of created statements
and result
  +                    sets, so close statements and result sets after use.
  +                </p>
  +                <p>
  +                    For read-only operations there is no need to start a PB-tx.
  +                </p>
                   <note>
                       Do not commit the connection instance, this will be done by OJB when
PersistenceBroker
                       commit-/abortTransaction was called.
  +                    <br/>
  +                    Never do a <code>Connection.close()</code> call on the
obtained connection instance
  +                    by hand!!
  +                    <br/>
  +                    This will be handled by the
  +                    <link href="#connection-factory"><em>ConnectionFactory</em></link>.
                   </note>
                   <p>
  -                    If no transaction was running, it is possible to release connection
after
  -                    use  by hand:
  +                    If <strong>no</strong> transaction is running, it is possible
to release a connection after
  +                    use by hand with call:
                   </p>
  -                <source>
  -pBroker.serviceConnectionManager().releaseConnection();
  -                </source>
  +                <source><![CDATA[
  +pBroker.serviceConnectionManager().releaseConnection();]]></source>
                   <p>
                       This call cleanup the used connection and pass the instance to release
method
                       of <link href="#connection-factory"><em>ConnectionFactory</em></link>
(this will e.g.
                       return connection it to pool or close it).
  +                </p>
  +                <p>
                       If you don't do any connection cleanup at the latest the connection
will be released
                       on PB.close() call.
                   </p>
  -                <note>
  -                    Never do a <code>Connection.close()</code> call on the
obtained connection instance
  -                    by hand!!
  -                    <br/>
  -                    This will be handled by the
  -                    <link href="#connection-factory"><em>ConnectionFactory</em></link>.
  -                </note>
                   <p>
                       Users who interested in this section also interested in
                       <link href="site:faq/performSQL">'Is it possible to perform my
own sql-queries in OJB?'</link>.
  
  
  
  1.1.2.1   +75 -47    db-ojb/src/doc/forrest/src/documentation/content/xdocs/docu/guides/deployment.xml
  
  Index: deployment.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/src/doc/forrest/src/documentation/content/xdocs/docu/guides/deployment.xml,v
  retrieving revision 1.1
  retrieving revision 1.1.2.1
  diff -u -r1.1 -r1.1.2.1
  --- deployment.xml	20 Jun 2004 09:12:33 -0000	1.1
  +++ deployment.xml	27 Jul 2004 00:29:31 -0000	1.1.2.1
  @@ -95,61 +95,89 @@
   
               <anchor id="additional-jars"/>
               <section>
  -                <title>3. Additional jar archives</title>
  +                <title>3. External dependencies that do not come with OJB</title>
                   <p>
  -                    OJB depends on several other jar archives. These jar files are
  -                    shipped in the
  -                    <code>db-ojb-&lt;version&gt;/lib</code> directory.
  -                    <link href="http://db.apache.org/ojb/dependencies.html">These
jar files are listed here.</link>
  +                    Some components of OJB depend on external libraries and components
that
  +                    cannot be shipped with OJB. You'll also need these if you want to compile
  +                    OJB from source. Here is a list of these dependencies:
                   </p>
  +                <dl>
  +                    <dt><code>j2ee.jar</code></dt>
  +                    <dd>
  +                        This is the main archive of the <link href="ext:sun/j2ee-sdk">J2EE
SDK</link>.
  +                        We recommend that you use the 1.3 version as the 1.4 is rather
new and not
  +                        thoroughly tested yet with OJB.
  +                    </dd>
  +                    <dt><code>jdo.jar, jdori*.jar</code></dt>
  +                    <dd>
  +                        The <link href="ext:sun/jdo">JDO Reference implementation</link>
is required
  +                        if you plan to use the JDO Api.
  +                    </dd>
  +                </dl>
  +            </section>
  +
  +            <anchor id="optional-jars"/>
  +            <section>
  +                <title>4. Optional jar archives that come with OJB</title>
                   <p>
  -                    Some of these jar files are only used during build-time and need not
to be
  -                    be deployed in runtime environments.
  +                    Some of jar files in the <code>lib</code> folder are only
used during build-time
  +                    or are only required by certain components of OJB, and so they might
need not to
  +                    be needed in runtime environments.
                       <br/>
  -                    Apart from wasting disk space they do no harm. If you don't care you
just take all jars from
  -                    <code>db-ojb-&lt;version&gt;/lib</code>.
  +                    Apart from wasting disk space they do no harm. If you don't care about
disk space
  +                    you just take all jars from the <code>lib</code> folder.
                       <br/>
  -                    If you do care, here is the list of jars you can omit during runtime:
  +                    If you do care, here is the list of jars you might omit during runtime:
                   </p>
  -                <ul>
  -                    <li>
  -                        <code>ant.jar</code>
  -                    </li>
  -                    <li>
  -                        <code>antlr.debug.jar</code>
  -                    </li>
  -                    <li>
  -                        <code>antlr_compiletime.jar</code>
  -                    </li>
  -                    <li>
  -                        <code>junit.jar</code>
  -                    </li>
  -                    <li>
  -                        <code>optional.jar</code>
  -                    </li>
  -                    <li>
  -                        <code>xalan.jar</code>
  -                    </li>
  -                    <li>
  -                        <code>ejb.jar</code>
  -                    </li>
  -                    <li>
  -                        <code>servlet.jar</code>
  -                    </li>
  -                    <li>
  -                        <code>jakarta-regexp-xxx.jar</code>
  -                    </li>
  -                    <li>
  -                        <code>torque-xxx.jar</code>
  -                    </li>
  -                    <li>
  -                        <code>velocity-xxx.jar</code>
  -                    </li>
  -                </ul>
  +                <dl>
  +                    <dt><code>ant-*.jar</code></dt>
  +                    <dd>
  +                        These are the <link href="ext:ant">Apache Ant 1.6</link>
jars.
  +                    </dd>
  +                    <dt><code>antlr-[version].jar</code></dt>
  +                    <dd>
  +                        <link href="ext:antlr">ANTLR</link> is a parser generator
which is
  +                        used in the ODMG component of OJB. If you only use the PB Api,
then you
  +                        don't need this.
  +                    </dd>
  +                    <dt><code>junit.jar</code></dt>
  +                    <dd>
  +                        <link href="ext:junit">Junit</link> for running the
unit tests. You'll need
  +                        this only if you're also writing unit tests for you app.
  +                    </dd>
  +                    <dt><code>xerces.jar, xml-apis.jar</code></dt>
  +                    <dd>
  +                        The <link href="ext:xml-apache/xerces">Xerces</link>
XML parser. Since most newer
  +                        JDK's ship with an XML parser, it is likely that you do not need
these files.
  +                    </dd>
  +                    <dt><code>xalan.jar</code></dt>
  +                    <dd>
  +                        <link href="ext:xml-apache/xalan">Xalan</link> is used
to generate the unit test report,
  +                        so you'll probably don't need this.
  +                    </dd>
  +                    <dt><code>jakarta-regexp-[version].jar</code></dt>
  +                    <dd>
  +                        The <link href="ext:jakarta/regexp">Jakarta Regular Expression
library</link> is
  +                        only used when building OJB from source.
  +                    </dd>
  +                    <dt><code>torque-xxx.jar, velocity-xxx.jar</code></dt>
  +                    <dd>
  +                        <link href="ext:torque">Torque</link> is used to generate
concrete databases
  +                        from database-independent schema files. OJB uses it internally
to setup databases
  +                        for the unit tests.
  +                    </dd>
  +                    <dt><code>xdoclet-[version].jar, xjavadoc-[version].jar,
xdoclet-ojb-module-[version].jar, commons-collections-[version].jar</code></dt>
  +                    <dd>
  +                        The <link href="site:xdoclet-module">XDoclet OJB module</link>
can be used
  +                        to generate the repository metadata and Torque schema files from
Javadoc comments
  +                        in the Java source files. It is however not required at runtime,
so you can safely
  +                        ignore these files then.
  +                    </dd>
  +                </dl>
               </section>
   
               <section>
  -                <title>4. Don't forget the JDBC driver</title>
  +                <title>5. Don't forget the JDBC driver</title>
                   <p>
                       The repository.xml defines JDBC Connections
                       to your runtime databases. To use the declared JDBC drivers the
  
  
  
  1.1.2.1   +11 -1     db-ojb/src/doc/forrest/src/documentation/content/xdocs/docu/guides/platforms.xml
  
  Index: platforms.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/src/doc/forrest/src/documentation/content/xdocs/docu/guides/platforms.xml,v
  retrieving revision 1.1
  retrieving revision 1.1.2.1
  diff -u -r1.1 -r1.1.2.1
  --- platforms.xml	20 Jun 2004 09:12:33 -0000	1.1
  +++ platforms.xml	27 Jul 2004 00:29:31 -0000	1.1.2.1
  @@ -41,6 +41,11 @@
                   This document explains basic concepts and shows how OJB can be
                   configured to run against a specific RDBMS.
               </p>
  +            <p>
  +                If you not already have done so, then you also might want to have a
  +                look at the <link href="site:getting-started">Getting Started</link>
  +                section which presents a sample skeleton project.
  +            </p>
           </section>
           <section>
               <title>Basic Concepts</title>
  @@ -183,6 +188,11 @@
                   <p>
                       The o/r mappings for these tables are contained in the file
                       <code>repository_internal.xml</code>.
  +                </p>
  +                <p>
  +                    If you want to have a look at how these files could be used,
  +                    have a look at the the <link href="site:getting-started">ojb-blank</link>
  +                    sample project which is already prepared to use these files.
                   </p>
   
               </section>
  
  
  
  No                   revision
  No                   revision
  1.1.2.1   +28 -2     db-ojb/src/doc/forrest/src/documentation/content/xdocs/docu/tutorials/pb-tutorial.xml
  
  Index: pb-tutorial.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/src/doc/forrest/src/documentation/content/xdocs/docu/tutorials/pb-tutorial.xml,v
  retrieving revision 1.1
  retrieving revision 1.1.2.1
  diff -u -r1.1 -r1.1.2.1
  --- pb-tutorial.xml	20 Jun 2004 09:12:33 -0000	1.1
  +++ pb-tutorial.xml	27 Jul 2004 00:29:31 -0000	1.1.2.1
  @@ -204,11 +204,13 @@
               </section>
   
   
  +            <anchor id="query-objects"/>
               <section>
                   <title>Querying Persistent Objects</title>
                   <p>
                       Once objects have been stored to the database, it is important to be
able to get them
  -                    back. The PersistenceBroker API provides two mechanisms for building
queries, by
  +                    back. The PersistenceBroker API provides two mechanisms for
  +                    <link href="site:query">building queries</link>, by
                       using a template object, or by using specific criteria.
                   </p>
                   <source><![CDATA[
  @@ -419,6 +421,30 @@
                       This method simply deletes an object from the database.
                   </p>
               </section>
  +
  +            <anchor id="find-by-pk"/>
  +            <section>
  +                <title>Find object by primary key</title>
  +                <p>
  +                    In some cases only the primary key values (single field or n-fields
for composed primary
  +                    keys) of an object are known. In OJB you have several ways to request
the whole object.
  +                    It is possible to build a query as
  +                    <link href="#query-objects">shown above</link>, but the
smarter
  +                    solution is to use <code>PersistenceBroker#getObjectByIdentity(Identity
oid)</code>. An
  +                    <link href="ext:identity">Identity</link> object is a unique
representation of a persistence
  +                    capable object based on the object primary key values and the <em>top-level
class</em> (abstract class,
  +                    interface or the class itself, depending on the
  +                    <link href="site:advanced-technique/extents">extent metadata
mapping</link>).
  +                </p>
  +                <p>
  +                    For example, to find an <em>Product</em> with an single
primary key of <em>'23'</em>
  +                    do
  +                </p>
  +                <source><![CDATA[
  +Identity oid = broker.serviceIdentity().buildIdentity(Product.class, new Integer(23));
  +Product product = (Product) broker.getObjectByIdentity(oid);]]></source>
  +            </section>
  +
           </section>
   
   
  
  
  
  No                   revision
  No                   revision
  1.1.2.1   +32 -1     db-ojb/src/doc/forrest/src/documentation/content/xdocs/docu/faq.xml
  
  Index: faq.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/src/doc/forrest/src/documentation/content/xdocs/docu/faq.xml,v
  retrieving revision 1.1
  retrieving revision 1.1.2.1
  diff -u -r1.1 -r1.1.2.1
  --- faq.xml	20 Jun 2004 09:12:35 -0000	1.1
  +++ faq.xml	27 Jul 2004 00:29:31 -0000	1.1.2.1
  @@ -829,6 +829,37 @@
               </answer>
           </faq>
   
  +
  +        <faq id="primitiveNull">
  +            <question>
  +                How does OJB manage 'null' for primitive primary key?
  +            </question>
  +            <answer>
  +                <p>
  +                    Primitive values (int, long, ...) can't be <code>null</code>,
so OJB interpret '0' as <code>null</code>
  +                    for primitive PK/FK fields in persistent objects. Thus primitive PK
fields of persistent objects should
  +                    never be represented by a '0' value in DB and never used as a
  +                    <link href="site:sequence-manager">sequence key</link>
value.
  +                    <br/>
  +                    This is only true for primitive PK/FK fields (e.g. <code>Integer(0)</code>
is allowed).
  +                    All other fields have 'normal' behavior.
  +                </p>
  +            </answer>
  +        </faq>
  +
  +
  +        <faq id="lookupByPK">
  +            <question>
  +                How to lookup object by primary key?
  +            </question>
  +            <answer>
  +                <p>
  +                    Please see <link href="site:pb-tutorial/find-by-pk">PB tutorial
section</link>.
  +                </p>
  +            </answer>
  +        </faq>
  +
  +
           <faq id="itOrCol">
               <question>
                   Difference between getIteratorByQuery() and getCollectionByQuery()?
  
  
  
  1.6.2.1   +10 -9     db-ojb/src/doc/forrest/src/documentation/content/xdocs/docu/getting-started.xml
  
  Index: getting-started.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/src/doc/forrest/src/documentation/content/xdocs/docu/getting-started.xml,v
  retrieving revision 1.6
  retrieving revision 1.6.2.1
  diff -u -r1.6 -r1.6.2.1
  --- getting-started.xml	26 Jun 2004 23:45:15 -0000	1.6
  +++ getting-started.xml	27 Jul 2004 00:29:31 -0000	1.6.2.1
  @@ -658,8 +658,8 @@
       protocol="jdbc"
       subprotocol="mysql"
       dbalias="//localhost/productmanager"
  -    username="root"
  -    password=""
  +    username="steve"
  +    password="secret"
       eager-release="false"
       batch-mode="false"
       useAutoCommit="1"
  @@ -732,17 +732,18 @@
   ]]></source>
                   <p>
                       Of course, you'll need to setup the <code>CLASSPATH</code>
before running
  -                    your application. You'll should add all jars except the ones for Torque
  -                    (<code>torque-[version].jar</code>, <code>velocity-[version].jar</code>
  -                    and <code>commons-collections-[version].jar</code>) and
for the XDoclet OJB
  -                    module (<code>xdoclet-[version].jar</code>, <code>xjavadoc-[version].jar</code>
  -                    and <code>xdoclet-ojb-module-[version].jar</code>).
  +                    your application. You'll should add all jars from the <code>lib</code>
  +                    folder except the ones for Torque (<code>torque-[version].jar</code>,
  +                    <code>velocity-[version].jar</code> and <code>commons-collections-[version].jar</code>)
  +                    and for the XDoclet OJB module (<code>xdoclet-[version].jar</code>,
  +                    <code>xjavadoc-[version].jar</code> and <code>xdoclet-ojb-module-[version].jar</code>).
                   </p>
                   <p>
                       It is important to note that OJB per default assumes the <code>OJB.properties</code>
                       and <code>OJB-logging.properties</code> files in the directory
where you're
                       starting the application. Hence, we changed to the <code>build/resources</code>
  -                    directory.
  +                    directory before running the application. This of course requires the
compiled
  +                    classes to be on the classpath, as well (directory <code>build/classes</code>).
                   </p>
                   <p>
                       Per default, the same applies to the other configuration files
  
  
  
  No                   revision
  No                   revision
  1.3.2.1   +15 -3     db-ojb/src/doc/forrest/src/documentation/content/xdocs/site.xml
  
  Index: site.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/src/doc/forrest/src/documentation/content/xdocs/site.xml,v
  retrieving revision 1.3
  retrieving revision 1.3.2.1
  diff -u -r1.3 -r1.3.2.1
  --- site.xml	20 Jun 2004 20:58:16 -0000	1.3
  +++ site.xml	27 Jul 2004 00:29:31 -0000	1.3.2.1
  @@ -72,6 +72,7 @@
                   <lookup-pb href="#lookupPB"/>
                   <lookup-odmg href="#lookupODMG"/>
                   <api-differences href="#differencesBetweenAPI"/>
  +                <primitive-null href="#primitiveNull"/>
           </faq>
           <javadoc label="Javadoc" href="ext:javadoc" description=""/>
           <getting-started label="Getting started" href="getting-started.html" description="summary
of docs"/>
  @@ -81,7 +82,9 @@
               <mapping-tutorial label="Mapping Tutorial" href="mapping-tutorial.html"
description="Mapping tutorial">
                   <metadata-mapping href="#metadata"/>
               </mapping-tutorial>
  -            <pb-tutorial label="The PB API" href="pb-tutorial.html" description="PB
tutorial"/>
  +            <pb-tutorial label="The PB API" href="pb-tutorial.html" description="PB
tutorial">
  +                <find-by-pk href="#find-by-pk"/>
  +            </pb-tutorial>
               <odmg-tutorial label="The ODMG API" href="odmg-tutorial.html" description="odmg
tutorial"/>
               <jdo-tutorial label="The JDO API" href="jdo-tutorial.html" description="jdo
tutorial"/>
               <otm-tutorial label="The OTM API" href="otm-tutorial.html" description="otm
tutorial"/>
  @@ -199,6 +202,8 @@
               <perf-test href="org/apache/ojb/performance/PerfTest.html"/>
               <perf-handle href="org/apache/ojb/performance/PerfHandle.html"/>
               <perf-article href="org/apache/ojb/performance/PerfArticle.html"/>
  +            <identity href="org/apache/ojb/broker/Identity.html"/>
  +            <identity-factory href="org/apache/ojb/broker/IdentityFactory.html"/>
           </api>
           <ojb>
               <wiki-page href="http://wiki.apache.org/db-ojb"/>
  @@ -260,13 +265,15 @@
               <commons-sql href="commons/sandbox/sql/"/>
               <commons-pool href="commons/pool/"/>
               <commons-dbcp href="commons/dbcp/"/>
  -            <jcs href="http://jakarta.apache.org/turbine/jcs/index.html"/>
  +            <jcs href="turbine/jcs/index.html"/>
               <jetspeed-2 href="http://portals.apache.org/jetspeed-2/"/>
  +            <regexp href="regexp/index.html"/>
           </jakarta>
           <log4j href="http://logging.apache.org/log4j/">
               <configuration href="docs/manual.html"/>
           </log4j>
           <ant href="http://ant.apache.org/"/>
  +        <antlr href="http://www.antlr.org/"/>
           <hsqldb href="http://hsqldb.sourceforge.net/"/>
           <mysql href="http://dev.mysql.com/">
               <driver href="downloads/connector/j/"/>
  @@ -298,9 +305,14 @@
               <jdo href="products/jdo/">
                   <javadoc href="javadocs/index.html"/>
               </jdo>
  +            <j2ee-sdk href="j2ee/1.3/download.html#sdk"/>
           </sun>
           <odmg-group href="http://www.odmg.org/"/>
           <junit href="http://www.junit.org"/>
  +        <xml-apache href="http://xml.apache.org/">
  +            <xerces href="xerces-j/"/>
  +            <xalan href="xalan-j/"/>
  +        </xml-apache>
           <tammi href="http://tammi.sourceforge.net/"/>
           <ojbc href="http://ojbc.sourceforge.net/"/>
           <intact href="http://www.ebi.ac.uk/intact/"/>
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org


Mime
View raw message