An Apache Maven project that creates a patch for a WildFly application server that adds the MariaDB JDBC driver as a base layer module. Creating and installing a patch is an alternative to configuring the module manually (i.e. by writing a module.xml that is placed in the modules folder together with the jar file). Building this project will create a single file that includes the module.xml, the jar file with the driver and, some meta data that allows you to install the driver via the management web-interface or the command line interface.

Set the WildFly and MariaDB version using the wildfly.version and mariadb.version properties of the pom.xml. Then run:

mvn clean package

Be aware that building the patch will download WildFly into your local Maven repository and it will unpack two instances of WildFly in the build folder. So make sure that you have enough free space on your disk. If you get build errors, try downgrading your Java Virtual Machine to version 1.8.

Apply the generated patch file (target/wildfly-${wildfly.version}-mariadb-${mariadb.version}-patch.zip) to your host(s) using the management web-interface of a standalone server or domain (see the patching section) or using the command line interface (bin/jboss-cli). For the latter, you would use the following commands:

connect <management-interface>	                        (e.g. connect http-remoting://localhost:9990)
patch apply <path-to-file-on-disk> --host=<host-name>   (e.g. patch apply /opt/patch.zip --host=master)

After patching, you will find the patch with some more meta data in the .installation folder. Don't forget to restart the patched host(s).

If you are patching a stopped standalone server, you can simply chdir to the root of the installation directory and run the following (quotation marks are intentional):

./bin/jboss-cli.sh "patch apply <path-to-file-on-disk>"

To use the JDBC driver, it must be added to the datasources subsystem in standalone.xml or domain.xml.

 <subsystem xmlns="urn:jboss:domain:datasources:7.1">
    <datasources>
        <datasource jndi-name="java:/mydatabase" pool-name="mydatabasedb" enabled="true" use-java-context="true">
            <connection-url>jdbc:mariadb://localhost:3306/mydatabase</connection-url>
            <driver>mariadb</driver>
            <security user-name="myusername" password="mypassword" />
        </datasource>
        <drivers>
            <driver name="h2" module="com.h2database.h2">
                <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
            </driver>
            <driver name="mariadb" module="org.mariadb.jdbc"/>
        </drivers>
    </datasources>
</subsystem>

Version 2.1.3.Final of the patch-gen Maven plugin (https://github.com/jbossas/patch-gen) does not (yet) support Wildfly 30.0.0.Final. I assume it will be patched soon. For the time being, you can get a copy from the patch-gen fork at https://github.com/locosmac/patch-gen and run mvn clean install to create a local 2.1.4.Final-SNAPSHOT patch-gen Maven plugin that works (for me).

The build logic is based on this very educating example from hibernate that creates a WildFly patch for some other module.

Maven, WildFly and MariaDB are most likely trademarks of their respective owners. This project is neither affilated with nor endorsed by Red Hat, Apache or MariaDB Corporation. I just like to use their cool products and mentioning Maven, WildFly and MariaDB seems to be necessary to describe the purpose and usage of this project.

Public domain, after all, it's only 3 XML files that you could have written yourself in less than half an hour, right? Use the code as fits and please, don't sue me for making it available for free. Thank you.