User: vharcq  
  Date: 01/06/23 09:12:29

  Modified:    src/docs customizingjaws.xml
  Log:
  JBoss 2.2 Compliance (not really a lot to do as there is no example in this chapter)
  
  Revision  Changes    Path
  1.10      +35 -6     manual/src/docs/customizingjaws.xml
  
  Index: customizingjaws.xml
  ===================================================================
  RCS file: /cvsroot/jboss/manual/src/docs/customizingjaws.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- customizingjaws.xml       2001/06/22 03:47:40     1.9
  +++ customizingjaws.xml       2001/06/23 16:12:29     1.10
  @@ -7,9 +7,18 @@
         </author>
         <email>[EMAIL PROTECTED]</email>
      </para>
  +   <para>JBoss 2.2 compliance checked by:<author>
  +                     <firstname>Vincent</firstname>
  +                     <surname>Harcq</surname>
  +             </author>
  +             <email>[EMAIL PROTECTED]</email>  
  +     </para>  
  +     
      <section>
         <title>Introduction</title>
  -      <para>JAWS is the O/R mapper used by JBoss to manage CMP entity beans. JAWS 
is configured in a file named standardjaws.xml, located in the conf/config-name 
directory in the JBoss distribution. The default <quote>config-name</quote> is 
<quote>default</quote>.</para>
  +      <para>JAWS is the O/R mapper used by JBoss to manage CMP entity beans. JAWS 
is configured in a file 
  +      named standardjaws.xml, located in the conf/config-name directory in the 
JBoss distribution. 
  +      The default <quote>config-name</quote> is <quote>default</quote>.</para>
   
   <para>This file configures JAWS for all JBoss. You can then extend
   this configuration on a per-application basis by putting a jaws.xml
  @@ -52,7 +61,7 @@
         <title>Specifying a datasource</title>
         <para>A datasource is, mainly, a database plus a driver plus a connection 
pool. By 
   default, jboss uses the Hypersonic datasource. To add another
  -datasource, you have to declare it as a JMX MLet: see the manual.</para>
  +datasource, you have to declare it as a JMX MLet: see <xref 
linkend="jdbc-database"/>.</para>
         <para>The second ARG of this MLet is the JNDI name of the datasource, i.e. 
the name 
   you have to use to access it. To tell JAWS to use this
   datasource, simply add in your jaws.xml file a <![CDATA[ <datasource>  tag 
  @@ -74,7 +83,7 @@
          </para>
            </listitem>       
            <listitem>
  -            <para>       Oracle
  +            <para>       Oracle 7/8
          </para>
            </listitem>       
            <listitem>
  @@ -94,6 +103,10 @@
          </para>
            </listitem>       
            <listitem>
  +            <para>       DB2
  +       </para>
  +         </listitem>       
  +         <listitem>
               <para>       DB2/400
          </para>
            </listitem>       
  @@ -101,6 +114,22 @@
               <para>       MS SQLSERVER
          </para>
            </listitem>       
  +         <listitem>
  +            <para>       InterBase
  +       </para>
  +         </listitem>
  +         <listitem>
  +            <para>       Sybase
  +       </para>
  +         </listitem>
  +         <listitem>
  +            <para>       SapDB
  +       </para>
  +         </listitem>
  +         <listitem>
  +            <para>       Cloudscape
  +       </para>
  +         </listitem>
         </itemizedlist>
         <para>For instance, if you want to use the Postgres Database that you have 
deployed 
   in jboss.conf under the name MyPostgresPool, this is how
  @@ -397,7 +426,7 @@
   </programlisting>
               </listitem>
               <listitem>
  -               <para>Declare your finder in jaws.xml, using the <![CDATA[<query>]]> 
tag. There are two options. The first presented here conforms to SQL92 and is the more 
generic and portable one. The second presented here is defined by T-SQL and is useful 
for MS Access 97 (and maybe more databases I'm not aware of).</para>
  +               <para>Declare your finder in jaws.xml, using the <![CDATA[<query>]]> 
tag. There are two options. The first presented here conforms to SQL92 and is the more 
generic and portable one. The second presented here is defined by T-SQL and is useful 
for MS Access 97 for example.</para>
                  <para>Generic SQL92 example:</para>
                  <programlisting><![CDATA[
   <finder>
  @@ -443,7 +472,7 @@
         </section>
   
         <section>
  -         <title>Advanced options for declared finders</title>
  +         <title>Advanced options for declared finders [since JBoss 2.4]</title>
            <para>Author:
               <author>
                  <firstname>Dan</firstname>
  @@ -451,7 +480,7 @@
               </author>
               <email>[EMAIL PROTECTED]</email> or <email>[EMAIL PROTECTED]</email>
            </para>
  -         <para>As of JBoss version 2.3 beta (6/15/2001), it is possible to request
  +         <para>As of JBoss version 2.4, it is possible to request
            that JAWS preload data for all entities selected by a declared finder. This
            avoids a performance problem where the database will be queried separately
            to load data for each bean returned by the finder. To activate this 
  
  
  

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to