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/docu/guides deployment.xml
Date Fri, 20 Aug 2004 09:34:22 GMT
arminw      2004/08/20 02:34:22

  Modified:    src/doc/forrest/src/documentation/content/xdocs/docu/guides
                        deployment.xml
  Log:
  update section about usage in managed environments
  
  Revision  Changes    Path
  1.4       +39 -45    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.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- deployment.xml	11 Aug 2004 00:46:56 -0000	1.3
  +++ deployment.xml	20 Aug 2004 09:34:22 -0000	1.4
  @@ -14,7 +14,9 @@
     See the License for the specific language governing permissions and
     limitations under the License.
   -->
  +
   <!-- @version $Id$ -->
  +
   <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "document-v12.dtd">
   
   <document>
  @@ -727,7 +729,7 @@
   //ODMG-api
   Implementation odmg = OJB.getInstance();]]></source>
                       <p>
  -                        But it is also possible to bind OJB api access classes to JNDI
and
  +                        But it is recommended to bind OJB api access classes to JNDI and
                           lookup the the api entry <link href="#bind-to-jndi">classes
via JNDI</link>.
                       </p>
                   </section>
  @@ -775,11 +777,11 @@
   
               <anchor id="example-beans"/>
               <section>
  -                <title>Build example beans</title>
  +                <title>Example Session Beans</title>
  +
  +                <anchor id="example-introduction"/>
                   <section>
  -                    <title>
  -                        <strong>Generate the sample session beans</strong>
  -                    </title>
  +                    <title>Introduction</title>
                       <p>
                           The OJB source distribution was shipped with a bunch of sample
                           session beans and client classes for testing. Please recognize
that we don't say that
  @@ -787,6 +789,18 @@
                           only one way to make it work.
                       </p>
                       <p>
  +                        To keep the examples as simple as possible we directly use the
OJB main classes
  +                        via static lookup or helper classes on each <em>ejbCreate()</em>
call. But we recommend to
  +                        <link href="#bind-to-jndi">bind the OJB main classes</link>
in JNDI instead of direct use
  +                        in the session beans.
  +                    </p>
  +                </section>
  +
  +                <section>
  +                    <title>
  +                        <strong>Generate the sample session beans</strong>
  +                    </title>
  +                    <p>
                           The source code of the sample beans is stored in directory
                           <br/>
                           <code>[db-ojb]/src/ejb/org/apache/ojb/ejb</code>
  @@ -979,20 +993,21 @@
                       Current bean examples do directly use OJB main classes, but it's also
possible to make
                       OJB accessible via JNDI and use a JNDI-lookup to access OJB api's in
your beans.
                       <br/>
  -                    To make the OJB api's accessible via JNDI, you can bind them to JNDI.
How to do
  -                    this depends on the used environment.
  -                    The main classes/method to bind are:
  +                    To make the OJB api's accessible via JNDI, bind main/access classes
to JNDI. How to do
  +                    this depends on the used environment. The main classes/methods to bind
are:
                   </p>
                   <ul>
                       <li>
  -                        Class
  -                        <code>org.apache.ojb.OJB</code> for PB-api.
  -                        Make an instance of this class accessible via JNDI.
  +                        PB-api:<br/>
  +                        Method <code>org.apache.ojb.broker.core.PersistenceBrokerFactoryFactory#instance()</code>
  +                        returns the used <code>org.apache.ojb.broker.core.PersistenceBrokerFactoryIF</code>.
Make
  +                        this instance accessible via JNDI.
                       </li>
                       <li>
  -                        Class
  -                        <code>org.apache.ojb.odmg.OJB</code> for ODMG-api.
Make method
  -                        <code>OJB.getInstance()</code> accessible.
  +                        ODMG-api:<br/>
  +                        Method <code>org.apache.ojb.odmg.OJB#getInstance()</code>
returns a new instance of
  +                        the <code>org.odmg.Implementation</code> instance.
Open a new <code>Database</code>and
  +                        make this instance and the <code>Database</code> instance
accessible via JNDI.
                       </li>
                   </ul>
   
  @@ -1001,31 +1016,13 @@
                           <strong>JBoss</strong>
                       </title>
                       <p>
  -                    In JBoss you can use
  -                    <code>mbean</code> classes.
  -                    <code>org.apache.ojb.jboss.PBFactory</code> and
  -                    <code>org.apache.ojb.jboss.ODMGFactory</code>
  -                    are mbean implementations bind PB-api and ODMG-api main classes to
JNDI.
  -                    <br/>
  -                    Let JBoss know about the new mbeans, so declare them in a
  -                    <code>jboss-service.xml</code> file:
  -                        </p>
  -                    <source><![CDATA[
  -<?xml version="1.0" encoding="UTF-8"?>
  -
  -<server>
  -    <mbean code="org.apache.ojb.jboss.PBFactory"
  -        name="DefaultDomain:service=PBAPI,name=ojb/PBAPI">
  -        <depends>jboss.jca:service=RARDeployer</depends>
  -        <attribute name="JndiName">ojb/PBAPI</attribute>
  -    </mbean>
  -
  -    <mbean code="org.apache.ojb.jboss.ODMGFactory"
  -    name="DefaultDomain:service=ODMG,name=ojb/defaultODMG">
  -        <depends>jboss.jca:service=RARDeployer</depends>
  -        <attribute name="JndiName">ojb/defaultODMG</attribute>
  -    </mbean>
  -</server>]]></source>
  +                        In JBoss you can write <em>mbean</em> classes to bind
OJB main/access classes to JNDI,
  +                        similar to the <link href="#pb.factory"><em>Weblogic</em>
example</link> below.
  +                        <br/>
  +                        Let JBoss know about the new mbeans, so declare them in a
  +                        <code>jboss-service.xml</code> file. Please see JBoss
documentation how to write mbeans
  +                        and bind objects to JNDI.
  +                    </p>
                   </section>
   
                   <section>
  @@ -1034,11 +1031,8 @@
                       </title>
                       <p>
                           In other application server you can do similar steps to bind OJB
main api classes to
  -                        JNDI. For example in Weblogic you can use
  -                        <em>startup class
  -                        </em> implementation
  -                        (see
  -                        <link href="#weblogic">below</link>).
  +                        JNDI. For example in Weblogic you can use <em>startup class</em>
implementation to bind
  +                        OJB main/access classes to JNDI (see <link href="#weblogic">below</link>).
                       </p>
                   </section>
               </section>
  
  
  

---------------------------------------------------------------------
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