Minerva is going to be maintained outside of JBoss from now on.
So in the future, we'll just have a "minerva.jar" in the lib/ext directory
instead of all the code under "org/jboss/minerva". This is the transition
period, where both exist. The JDBCDataSourceLoader and XADataSourceLoader
have been changed to use the new Minerva, and once the Connector code has
been updated as well, we'll remove the Minerva code from
"org/jboss/minerva".
Further, once the Connector code is solid, we'll either deprecate
JDBCDataSourceLoader and XADataSourceLoader, or change the implementations
to use Connectors instead. In either case, all the client code will be
the same (you still get a javax.sql.DataSource in JNDI), it's just the
server configuration that would change.
So, there's only one immediate impact: When you're using the
Minerva XA wrappers for JDBC drivers, you need to change the class name
org.jboss.minerva.xa.XADataSourceImpl
to
org.opentools.minerva.jdbc.xa.wrapper.XADataSourceImpl
(Sorry to make it longer! :) I've made the change in the default
configuration file, and it passes the "jbosstest" testbeantest (well, at
least as much as it passed before).
The current rev of Minerva adds a configurable limit to the number
of PreparedStatements that are cached in each Connection (with which you
should be able to solve the "exceeded maximum open cursors" Oracle error),
and J2EE Connector support.
Aaron
