User: mulder
Date: 00/09/13 05:14:02
Modified: src/main/org/jboss/minerva/datasource PoolDriver.java
Log:
More JavaDoc comment updates.
Make sure the pools are unloaded correctly with the new names.
Revision Changes Path
1.5 +8 -8 jboss/src/main/org/jboss/minerva/datasource/PoolDriver.java
Index: PoolDriver.java
===================================================================
RCS file:
/products/cvs/ejboss/jboss/src/main/org/jboss/minerva/datasource/PoolDriver.java,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- PoolDriver.java 2000/09/13 12:07:05 1.4
+++ PoolDriver.java 2000/09/13 12:14:02 1.5
@@ -17,16 +17,16 @@
* java.sql.Connection back in any case (in the case of XAConnections, the
* transactional-ness is handled under the covers). You must create the pools
* ahead of time by creating and initializing the appropriate DataSource.
- * <TABLE BORDER="1">
- * <TR><TH>Connection Type</TH><TH>URL Form</TH></TR>
- * <TR><TD>Connection</TD><TD>jdbc:minerva:<I>PoolName</I></TD></TR>
- * <TR><TD>XAConnection</TD><TD>jdbc:minervaxa:<I>PoolName</I></TD></TR>
- * </TABLE>
- * <P>Note that you must load this driver like normal in order to use it:<BR>
- * <CODE>Class.forName("org.minerva.datasource.PoolDriver");</CODE></P>
+ * <P>You should use a URL of the form <B>jdbc:minerva:<I>PoolName</I></B>
+ * to get a connection from the pool. This will check for both a JDBC Pool
+ * and XA Pool if necessary, so don't create one pool of each type with the
+ * same name!</P>
+ * <P>This driver will be loaded automatically whenever a JDBC Pool or XA
+ * Pool is created, but you can also use the standard <CODE>Class.forName</CODE>
+ * call to load it.</P>
* @see org.jboss.minerva.datasource.JDBCPoolDataSource
* @see org.jboss.minerva.datasource.XAPoolDataSource
- * @version $Revision: 1.4 $
+ * @version $Revision: 1.5 $
* @author Aaron Mulder ([EMAIL PROTECTED])
*/
public class PoolDriver implements Driver {
