How to use a different version (slot) of a datasource driver?

[aqtwrdnr]

Hello,

In relation to my previous (until now unanswered) question: How to load an embedded h2 database dynamically from a singleton EJB.

I am trying to use a newer version of h2 databse than the one provided with JBoss 7.2.0.Final. I have installed the newer version of the h2 module by placing a module.xml (together with h2-1.3.176.jar) in the $JBOSS_HOME/modules/com/h2database/h2/1.3.176 folder with the following contents:

<?xml version="1.0" encoding="UTF-8"?>

<module xmlns="urn:jboss:module:1.1" name="com.h2database.h2" slot="1.3.176">

    <resources>

        <resource-root path="h2-1.3.176.jar"/>

        <!-- Insert resources here -->

    </resources>

    <dependencies>

        <module name="javax.api"/>

        <module name="javax.transaction.api"/>

        <module name="javax.servlet.api" optional="true"/>

    </dependencies>

</module>

Now I would like to not use the 'main' version of the h2 module for my datasource, but version '1.3.176'. I cannot find any (official) documentation about how to achieve this, but I've tried adding the following configuration to the drivers section in the standalone.xml:

<driver name="h2" module="com.h2database.h2" slot="1.3.176">

    <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>

</driver>

Although the 'slot' attribute is not documented in the datasource XSD schema.

However, it does not seem to pick it up, correctly.

How can I check which version of the module is actually loaded? And how can I specify a slot in the driver element?

Thanks in advance!

Barry

[jaikiran]

It doesn't look like the slot attribute is supported for the driver element in the configuration, even with the latest WildFly. Maybe you could file a feature request for it here https://issues.jboss.org/browse/WFLY

A workaround for now is to define the module with a different name (and of course, place it in the right location in the modules directory) and use that module in your driver element configuration.

[ctomc]

AFAIR there was some change / fix for this to allow configuration like this

<driver name="h2" module="com.h2database.h2:1.3.176">

note the :1.3.176 part.

[jaysensharma]

Barry,

    Try adding the module=<module-name>:<slot> while defining the driver, As following (suppose your oracle module slots are  "1.0" and "main" then in order to use the slot 1.0 use the following):

/subsystem=datasources/jdbc-driver=ojdbc6/:add(driver-module-name=com.oracle.jdbc6:1.0,driver-name=ojdbc6,jdbc-compliant=false)

See : https://issues.jboss.org/browse/AS7-3654

[aqtwrdnr]

Thanks for the (quick) answers. I have not (yet) had the time to test whether the proposed solution actually works, but I'll assume it does.

Kind regards,

Barry