User: mulder
Date: 00/09/13 05:53:35
Modified: minerva/examples index.html jboss.xml.txt
Log:
Update Minerva to 0.99. This includes the removal of "jdbc." and "xa."
prefixes from JNDI and the "jdbc:minervaxa:" URL prefix.
Please sync this to the web site when the BETA-PROD is released.
Revision Changes Path
1.2 +1 -1 jbossweb/minerva/examples/index.html
Index: index.html
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/minerva/examples/index.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- index.html 2000/09/06 15:06:42 1.1
+++ index.html 2000/09/13 12:53:34 1.2
@@ -57,7 +57,7 @@
sometimes loaded after the auto-deployer, so your beans try to deploy
before the pools exist. In that case, they tend to get naming
exceptions and fail to deploy. Look for an output line like:<BR>
- <CODE>[XADataSource] XA Connection pool foo bound to xa.foo</CODE><BR>
+ <CODE>[XADataSource] XA Connection pool foo bound to foo</CODE><BR>
and that is when the pool has started.</P>
<P>If this is the case for you, there's little you can do. Sometimes if
you try again it will work, since it seems to be dependent in some way
1.2 +1 -1 jbossweb/minerva/examples/jboss.xml.txt
Index: jboss.xml.txt
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/minerva/examples/jboss.xml.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- jboss.xml.txt 2000/09/06 15:06:42 1.1
+++ jboss.xml.txt 2000/09/13 12:53:34 1.2
@@ -23,7 +23,7 @@
<resource-managers>
<resource-manager res-class="org.jboss.ejb.deployment.JDBCResource">
<res-name>OracleDBResource</res-name>
- <res-jndi-name>xa.OracleDB</res-jndi-name>
+ <res-jndi-name>OracleDB</res-jndi-name>
</resource-manager>
</resource-managers>
<enterprise-beans>
