I am clearly missing something. Why would I want to use the minerva driver
manager? Is it an internals developer thing? I've setup a pool in
jboss.jcml/jboss.conf, find the datasource using JNDI from my entity beans.
Cheers
-----Original Message-----
From: Aaron Mulder [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 13, 2000 11:01 AM
To: jBoss User List; jBoss Developer
Subject: [jBoss-Dev] Minerva Update
I've updated Minerva in CVS, but I think we'll release the new
documentation in concert with the BETA-PROD release. So I'll describe the
changes here for anyone using the CVS code, and you can ignore them if
you're using a binary.
Basically, there is no longer an "xa." or "jdbc." prefix on the
beginning of a data source. If you specify your pool name as "foo" it
will be registered in JNDI under the name "foo" not "xa.foo". Also, you
no longer need to distinguish "xa" when constructing a JDBC URL to use
with the DriverManager - all pools use "jdbc:minerva:PoolName" now.
Finally, the default Hypersonic data source now uses Minerva.
Aaron
