User: tobias  
  Date: 01/01/03 09:23:43

  Modified:    manual   adv_config.html msjetenginejawstypemapping.txt
  Added:       manual   msjetenginejawstypemappingforjdbcodbc.txt
  Log:
  updated type mapping for MS Jet Engine/Access.
  Thanks to Michel de Groot
  
  Revision  Changes    Path
  1.4       +30 -28    newsite/manual/adv_config.html
  
  Index: adv_config.html
  ===================================================================
  RCS file: /products/cvs/ejboss/newsite/manual/adv_config.html,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- adv_config.html   2000/12/17 20:24:27     1.3
  +++ adv_config.html   2001/01/03 17:23:43     1.4
  @@ -673,43 +673,45 @@
         <li>CMP mapping in jaws.xml:<br>
         mySQL</li>
         </ul>
  -       <li>Microsoft Jet Engine/Access 97
  -         <ul> 
  -        <li>Driver Notes
  -          <ul> 
  -            <li>This example uses Sun's Jdbc-Odbc bridge. This type 1 JDBC driver 
can suffer from low performance but is very convenient if you start working with 
jBoss-Jet Engine. 
  -            </li> 
  -            <li>The ODBC data source can be created using Control Panel - ODBC Data 
Sources.
  -            </li>
  -            <li>Access and jBoss <em>cannot</em> open the datasource at the same 
time, but they can in turn (so you can use Access 97 as editor, viewer, bulk importer 
and exporter).
  -            </li>
  -          </ul> 
  -          <li>lib/ext: Sun JRE's rt.jar if your not running on a Sun virtual 
machine, otherwise none</li>
  -          <li>jboss.properties
  -             <pre> jdbc.drivers=sun.jdbc.odbc.JdbcOdbcDriver
  -             </pre> 
  -          </li> 
  -          <li>jboss.conf
  -             <pre> &lt;MLET CODE="org.jboss.jdbc.XADataSourceLoader" 
ARCHIVE="jboss.jar" CODEBASE="../lib/ext/"&gt;
  +
  +      <li>Microsoft Jet Engine/Access 97
  +        <ul> 
  +       <li>Driver Notes
  +            <ul> 
  +           <li>This example uses Sun's Jdbc-Odbc bridge. This type 1 JDBC driver is 
very convenient if you start working with JBoss-Jet Engine. It can be slow under heavy 
loads and should be replaced in high-load production environments. Also, the driver 
supports only JDBC 1, so JDBC 2.0 types like CLOB cannot be used.
  +             </li> 
  +             <li>The ODBC data source can be created using Control Panel - ODBC 
Data Sources.
  +             </li>
  +             <li>You can let Access and JBoss use the datasource at the same time. 
To do this, start JBoss first, then start Access. Access will open the datasource in 
Shared Mode. You can now use Access 97 as editor, viewer, bulk importer/exporter and 
query builder while JBoss can be stopped and started concurrently.
  +             </li>
  +           </ul> 
  +         <li>lib/ext: Sun JRE's rt.jar if your not running on a Sun virtual 
machine, otherwise none</li>             
  +         <li>jboss.properties
  +                     <pre> jdbc.drivers=sun.jdbc.odbc.JdbcOdbcDriver
  +                     </pre> 
  +         </li> 
  +         <li>jboss.conf
  +                     <pre> &lt;MLET CODE="org.jboss.jdbc.XADataSourceLoader" 
ARCHIVE="jboss.jar" CODEBASE="../lib/ext/"&gt;
           &lt;ARG TYPE="java.lang.String" VALUE="<b>JetEngineDB</b>"&gt;
           &lt;ARG TYPE="java.lang.String" 
VALUE="org.jboss.minerva.xa.XADataSourceImpl"&gt;
       &lt;/MLET&gt;
  - </pre> 
  -          </li> 
  -          <li>jboss.jcml
  +                     </pre> 
  +             </li> 
  +             <li>jboss.jcml
                        <pre> &lt;mbean 
name="DefaultDomain:service=XADataSource,name=<b>JetEngineDB</b>"&gt;
           &lt;attribute name="URL"&gt;jdbc:odbc:<b>ODBC datasource 
name</b>&lt;/attribute&gt;
           &lt;attribute name="JDBCUser"&gt;<b></b>&lt;/attribute&gt;
           &lt;attribute name="Password"&gt;<b></b>&lt;/attribute&gt;
       &lt;/mbean&gt;
                        </pre> 
  -Note: a default Jet Engine data source has no user and password, therefor the 
JDBCUser and Password attributes are empty. If you need a user or a password, see the 
other examples.
  -          </li> 
  -          <li>CMP Type Mapping Name (for jaws.xml): <code>MS Jet Engine</code><br>
  -             <a href="./msjetenginejawstypemapping.txt">You can download this 
mapping here.</a> Add the contents to your jaws.xml in the type-mappings section.
  -          </li> 
  -        </ul> 
  -      </li>   
  +                     Note: a default Jet Engine data source has no user and 
password, therefor the JDBCUser and Password attributes are empty. If you need a user 
or a password, see the other examples.
  +             </li> 
  +             <li>CMP Type Mapping Name (for jaws.xml): <code>MS Jet Engine</code> 
<br>
  +                 You can <a href="msjetenginejawstypemapping.txt">download this 
mapping here (if using JdbcOdbc bridge driver)</a> or <a 
href="msjetenginejawstypemappingforjdbcodbc.txt">here (if using JDBC 2.0 compliant 
driver)</a>. Add the contents to your jaws.xml in the type-mappings section.
  +             </li> 
  +     </ul> 
  +    </li>   
  +
       </ul>
   
   
  
  
  
  1.2       +68 -63    newsite/manual/msjetenginejawstypemapping.txt
  
  Index: msjetenginejawstypemapping.txt
  ===================================================================
  RCS file: /products/cvs/ejboss/newsite/manual/msjetenginejawstypemapping.txt,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- msjetenginejawstypemapping.txt    2000/12/17 20:24:27     1.1
  +++ msjetenginejawstypemapping.txt    2001/01/03 17:23:43     1.2
  @@ -1,63 +1,68 @@
  -     <type-mapping>
  -             <name>MS Jet Engine</name>
  -             <mapping>
  -                     <java-type>java.lang.Integer</java-type>
  -                     <jdbc-type>INTEGER</jdbc-type>
  -                     <sql-type>INTEGER</sql-type>
  -             </mapping>
  -             <mapping>
  -                     <java-type>java.lang.Character</java-type>
  -                     <jdbc-type>CHAR</jdbc-type>
  -                     <sql-type>CHAR(2)</sql-type>
  -             </mapping>
  -             <mapping>
  -                     <java-type>java.lang.Short</java-type>
  -                     <jdbc-type>SMALLINT</jdbc-type>
  -                     <sql-type>SMALLINT</sql-type>
  -             </mapping>
  -             <mapping>
  -                     <java-type>java.lang.Double</java-type>
  -                     <jdbc-type>DOUBLE</jdbc-type>
  -                     <sql-type>DOUBLE</sql-type>
  -             </mapping>
  -             <mapping>
  -                     <java-type>java.lang.Long</java-type>
  -                     <jdbc-type>DECIMAL</jdbc-type>
  -                     <sql-type>LONG</sql-type>
  -             </mapping>
  -             <mapping>
  -                     <java-type>java.lang.String</java-type>
  -                     <jdbc-type>VARCHAR</jdbc-type>
  -                     <sql-type>VARCHAR(255)</sql-type>
  -             </mapping>
  -             <mapping>
  -                     <java-type>java.lang.Object</java-type>
  -                     <jdbc-type>JAVA_OBJECT</jdbc-type>
  -                     <sql-type>IMAGE</sql-type>
  -             </mapping>
  -             <mapping>
  -                     <java-type>java.lang.Byte</java-type>
  -                     <jdbc-type>TINYINT</jdbc-type>
  -                     <sql-type>SMALLINT</sql-type>
  -             </mapping>
  -             <mapping>
  -                     <java-type>java.sql.TimeStamp</java-type>
  -                     <jdbc-type>TIMESTAMP</jdbc-type>
  -                     <sql-type>TIMESTAMP</sql-type>
  -             </mapping>
  -             <mapping>
  -                     <java-type>java.util.Date</java-type>
  -                     <jdbc-type>DATE</jdbc-type>
  -                     <sql-type>DATETIME</sql-type>
  -             </mapping>
  -             <mapping>
  -                     <java-type>java.lang.Boolean</java-type>
  -                     <jdbc-type>BIT</jdbc-type>
  -                     <sql-type>BIT</sql-type>
  -             </mapping>
  -             <mapping>
  -                     <java-type>java.lang.Float</java-type>
  -                     <jdbc-type>FLOAT</jdbc-type>
  -                     <sql-type>FLOAT</sql-type>
  -             </mapping>
  -     </type-mapping>
  +     <type-mapping>
  +             <name>MS Jet Engine</name>
  +             <mapping>
  +                     <java-type>java.lang.Integer</java-type>
  +                     <jdbc-type>INTEGER</jdbc-type>
  +                     <sql-type>INTEGER</sql-type>
  +             </mapping>
  +             <mapping>
  +                     <java-type>java.lang.Character</java-type>
  +                     <jdbc-type>CHAR</jdbc-type>
  +                     <sql-type>CHAR(2)</sql-type>
  +             </mapping>
  +             <mapping>
  +                     <java-type>java.lang.Short</java-type>
  +                     <jdbc-type>SMALLINT</jdbc-type>
  +                     <sql-type>SMALLINT</sql-type>
  +             </mapping>
  +             <mapping>
  +                     <java-type>java.lang.Double</java-type>
  +                     <jdbc-type>DOUBLE</jdbc-type>
  +                     <sql-type>DOUBLE</sql-type>
  +             </mapping>
  +             <mapping>
  +                     <java-type>java.lang.Long</java-type>
  +                     <jdbc-type>DECIMAL</jdbc-type>
  +                     <sql-type>LONG</sql-type>
  +             </mapping>
  +             <mapping>
  +                     <java-type>java.lang.String</java-type>
  +                     <jdbc-type>VARCHAR</jdbc-type>
  +                     <sql-type>VARCHAR(255)</sql-type>
  +             </mapping>
  +             <mapping>
  +                     <java-type>java.lang.Object</java-type>
  +                     <jdbc-type>JAVA_OBJECT</jdbc-type>
  +                     <sql-type>VARCHAR</sql-type>
  +             </mapping>
  +             <mapping>
  +                     <java-type>java.lang.Byte</java-type>
  +                     <jdbc-type>TINYINT</jdbc-type>
  +                     <sql-type>SMALLINT</sql-type>
  +             </mapping>
  +             <mapping>
  +                     <java-type>java.sql.TimeStamp</java-type>
  +                     <jdbc-type>TIMESTAMP</jdbc-type>
  +                     <sql-type>TIMESTAMP</sql-type>
  +             </mapping>
  +             <mapping>
  +                     <java-type>java.util.Date</java-type>
  +                     <jdbc-type>DATE</jdbc-type>
  +                     <sql-type>DATETIME</sql-type>
  +             </mapping>
  +             <mapping>
  +                     <java-type>java.lang.Boolean</java-type>
  +                     <jdbc-type>BIT</jdbc-type>
  +                     <sql-type>BIT</sql-type>
  +             </mapping>
  +             <mapping>
  +                     <java-type>java.lang.Float</java-type>
  +                     <jdbc-type>FLOAT</jdbc-type>
  +                     <sql-type>FLOAT</sql-type>
  +             </mapping>
  +             <mapping>
  +                     <java-type>java.lang.String</java-type>
  +                     <jdbc-type>CLOB</jdbc-type>
  +                     <sql-type>MEMO</sql-type>
  +             </mapping>
  +     </type-mapping>
  
  
  
  1.1                  newsite/manual/msjetenginejawstypemappingforjdbcodbc.txt
  
  Index: msjetenginejawstypemappingforjdbcodbc.txt
  ===================================================================
        <type-mapping>
                <name>MS Jet Engine</name>
                <mapping>
                        <java-type>java.lang.Integer</java-type>
                        <jdbc-type>INTEGER</jdbc-type>
                        <sql-type>INTEGER</sql-type>
                </mapping>
                <mapping>
                        <java-type>java.lang.Character</java-type>
                        <jdbc-type>CHAR</jdbc-type>
                        <sql-type>CHAR(2)</sql-type>
                </mapping>
                <mapping>
                        <java-type>java.lang.Short</java-type>
                        <jdbc-type>SMALLINT</jdbc-type>
                        <sql-type>SMALLINT</sql-type>
                </mapping>
                <mapping>
                        <java-type>java.lang.Double</java-type>
                        <jdbc-type>DOUBLE</jdbc-type>
                        <sql-type>DOUBLE</sql-type>
                </mapping>
                <mapping>
                        <java-type>java.lang.Long</java-type>
                        <jdbc-type>DECIMAL</jdbc-type>
                        <sql-type>LONG</sql-type>
                </mapping>
                <mapping>
                        <java-type>java.lang.String</java-type>
                        <jdbc-type>VARCHAR</jdbc-type>
                        <sql-type>VARCHAR(255)</sql-type>
                </mapping>
                <mapping>
                        <java-type>java.lang.Byte</java-type>
                        <jdbc-type>TINYINT</jdbc-type>
                        <sql-type>SMALLINT</sql-type>
                </mapping>
                <mapping>
                        <java-type>java.sql.TimeStamp</java-type>
                        <jdbc-type>TIMESTAMP</jdbc-type>
                        <sql-type>TIMESTAMP</sql-type>
                </mapping>
                <mapping>
                        <java-type>java.util.Date</java-type>
                        <jdbc-type>DATE</jdbc-type>
                        <sql-type>DATETIME</sql-type>
                </mapping>
                <mapping>
                        <java-type>java.lang.Boolean</java-type>
                        <jdbc-type>BIT</jdbc-type>
                        <sql-type>BIT</sql-type>
                </mapping>
                <mapping>
                        <java-type>java.lang.Float</java-type>
                        <jdbc-type>FLOAT</jdbc-type>
                        <sql-type>FLOAT</sql-type>
                </mapping>
        </type-mapping>
  
  
  

Reply via email to