jmcnally    02/05/24 00:04:40

  Modified:    xdocs    jdbc2pool-howto.xml
  Log:
  fix some html errors
  
  Revision  Changes    Path
  1.2       +8 -3      jakarta-turbine-torque/xdocs/jdbc2pool-howto.xml
  
  Index: jdbc2pool-howto.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-turbine-torque/xdocs/jdbc2pool-howto.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- jdbc2pool-howto.xml       24 May 2002 06:49:08 -0000      1.1
  +++ jdbc2pool-howto.xml       24 May 2002 07:04:40 -0000      1.2
  @@ -36,7 +36,7 @@
   If a pool is known to already be available via jndi, the configuration for
   torque to use it can be very simple.  In all examples that follow we will
   use the handle, bookstore.  This is the name attribute that is used in the
  -<database> tag in the schema.xml.  If the name attribute is not used, then the
  +&lt;database&gt; tag in the schema.xml.  If the name attribute is not used, then the
   handle would be 'default'.
   </p>
   
  @@ -76,7 +76,7 @@
   rules given in the class's javadoc.  If the default has not been configured,
   you can specify any other environment properties that are needed to instantiate
   the <code>InitialContext</code> as extra properties of the form,
  -torque.jndi.<handle>.<env-var>.  A couple examples are shown below:
  +torque.jndi.&lt;handle&gt;.&lt;env-var&gt;.  A couple examples are shown below:
   
   <source><![CDATA[
   torque.jndi.bookstore.java.naming.factory.initial = 
org.apache.naming.java.javaURLContextFactory
  @@ -141,6 +141,7 @@
   where the second handle, DBbookstore, has no relevance to torque, other than 
   to uniquely identify this group of properties as belonging together.  Any 
   unique handle may be used.
  +</p>
   
   </section>
   
  @@ -155,7 +156,7 @@
   used to come with torque, but is now part of commons-sandbox/jdbc2pool.
   </p>
   
  -<p>In server.xml, the following would be added to the <Context> for your
  +<p>In server.xml, the following would be added to the &lt;Context$gt; for your
   webapp:
   
   <source><![CDATA[
  @@ -214,6 +215,7 @@
   ]]></source>
   </p>
   
  +<p>
   Catalina deploys all objects configured similarly to above within the
   <strong>java:comp/env</strong> namespace so the jndi path given in
   Torque.properties would be
  @@ -226,13 +228,16 @@
   <code>ConnectionPoolDataSource</code>
   available via jndi under the name given in the dataSourceName, so you will
   need entries in server.xml and web.xml for this object as well.
  +</p>
   
  +<p>
   Catalina provides a default <code>DataSource</code> that can be used as well
   and it is configured similarly, but detailed information on that
   implementation is <a 
href="http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-resources-howto.html";>here</a>.
  Note that the 
   "type attribute/ref-type element" value of "javax.sql.DataSource" appears to 
   be reserved for catalina's default implementation, which is why the
   implementation classname is used in our configuration example.
  +</p>
   
   </section>
   
  
  
  

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to