You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-dev@db.apache.org by ar...@apache.org on 2004/06/19 11:30:35 UTC
cvs commit: db-ojb/forrest/src/documentation/content/xdocs/docu/guides deployment.xml
arminw 2004/06/19 02:30:35
Modified: forrest/src/documentation/content/xdocs/docu/guides
deployment.xml
Log:
update documentation, add example about how to build
deployable jar
Revision Changes Path
1.2 +55 -4 db-ojb/forrest/src/documentation/content/xdocs/docu/guides/deployment.xml
Index: deployment.xml
===================================================================
RCS file: /home/cvs/db-ojb/forrest/src/documentation/content/xdocs/docu/guides/deployment.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- deployment.xml 17 Jun 2004 12:28:11 -0000 1.1
+++ deployment.xml 19 Jun 2004 09:30:35 -0000 1.2
@@ -316,7 +316,7 @@
If the PB-api is the only persistence API being used (no ODMG nor JDO)
and it is
<strong>only</strong> being used in a managed environment, it is
- recommended to use a special PersistenceBrokerFactory class, which
+ strongly recommended to use a special PersistenceBrokerFactory class, which
enables PersistenceBroker instances to participate in the running JTA
transaction (e.g. this makes PBStateListener proper work in managed
environments and enables use of 'autoSync' property in ObjectCacheDefaultImpl):
@@ -625,11 +625,62 @@
/db-ojb-1.X.jar
/all used libraries]]></source>
+ </section>
+
+ <anchor id="deployable-jar"/>
+ <section>
+ <title>
+ <strong>7b. Example: Deployable jar</strong>
+ </title>
+ <p>
+ For example the jar-file used to test the <link href="#example-beans"><em>ejb-examples</em></link>
+ shipped with OJB, base on the <em>db-ojb-XY-beans.jar</em> file. This jar was created when the
+ <link href="#example-beans"><em>ejb-examples</em></link> target was called.
+ </p>
+ <p>
+ The generated jar contains only the ejb-classes and the deployment-descriptor. We have
+ to add additional jars (all libraries used by OJB) and files (all configuration files)
+ to make it deployable. The deployable <em>db-ojb-XY-beans.jar</em> should look like this:
+ </p>
+ <source><![CDATA[
+/OJB.properties
+/repository.dtd
+/repository.xml
+/repository_database.xml
+/repository_ejb.xml
+/repository_internal.xml
+/META-INF
+.../Manifest.mf
+.../ejb-jar.xml
+.../jboss.xml
+
+/org
+.../apache (all ejb classes)
+
+/db-ojb-1.X.jar
+
+/antlr-XXX.jar
+/commons-beanutils-XXX.jar
+/commons-collections-XXX.jar
+/commons-dbcp-XXX.jar
+/commons-lanf-XXX.jar
+/commons-logging-XXX.jar
+/commons-pool-XXX.jar
+/jakarta-regexp-XXX.jar]]></source>
+ <p>
+ Please pay attention on the <link href="#jboss-ojb.properties">configuration settings</link>
+ to make OJB work in managed environments (especially the OJB.properties settings).
+ </p>
<note>
- This described solution should be re-deployable in JBoss.
- <strong>If you will get any problems, please let me know. All suggestions are welcome</strong>
+ This example isn't a real world production example. Normally you will setup one or more enterprise
+ archive files (.ear files) to bundle one or more complete J2EE (web) applications. More about
+ how to build an <em>J2EE application</em> using OJB <link href="#packing-ear">see here</link>.
</note>
+ <p>
+ The described example should be re-deployable/hot-deployable in JBoss.
+ <br/><strong>If you will get any problems, please let me know. All suggestions are welcome!</strong>
+ </p>
</section>
<anchor id="howto-access"/>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org