<?xml version="1.0" encoding="UTF-8"?>
<!--
  ~ JBoss, Home of Professional Open Source.
  ~ Copyright 2010, Red Hat, Inc., and individual contributors
  ~ as indicated by the @author tags. See the copyright.txt file in the
  ~ distribution for a full listing of individual contributors.
  ~
  ~ This is free software; you can redistribute it and/or modify it
  ~ under the terms of the GNU Lesser General Public License as
  ~ published by the Free Software Foundation; either version 2.1 of
  ~ the License, or (at your option) any later version.
  ~
  ~ This software is distributed in the hope that it will be useful,
  ~ but WITHOUT ANY WARRANTY; without even the implied warranty of
  ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
  ~ Lesser General Public License for more details.
  ~
  ~ You should have received a copy of the GNU Lesser General Public
  ~ License along with this software; if not, write to the Free
  ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
  ~ 02110-1301 USA, or see the FSF site: http://www.fsf.org.
  -->
<module name="com.h2database.h2" xmlns="urn:jboss:module:1.9">

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

    <dependencies>
        <module name="java.compiler"/>
        <module name="java.desktop"/>
        <module name="java.instrument"/>
        <module name="java.logging"/>
        <module name="java.management"/>
        <module name="java.naming"/>
        <module name="java.scripting"/>
        <module name="java.sql"/>
        <!-- H2 uses Jakarta Servlet to allow apps (in our case deployments) to expose its console as a servlet.
             WildFly isn't concerning itself with allowing this H2 feature to continue to work in both a
             javax.* EE namespace and jakarta.* EE namespace environment, so this no longer works out of the box.
             But, we add an optional dep on a non-existent module as a hook to allow users to get it to work.
             Users who want this to work can provide a module with the name:slot javax.servlet.api:h2. That module could
             be a simple alias to the javax.servlet.api module the server provides, if that works with this module's
             H2 artifact. Or the user could provide a non-alias module that packages and exposes the servlet resources H2 needs. -->
        <module name="javax.servlet.api:h2" optional="true"/>
        <module name="org.slf4j"/>
    </dependencies>
</module>
