JBoss AS (known as WildFly) is well known application server that is supported out-of-box.
Recommended is to hold configuration strictly as JBoss module. It not depends on the name (in this page we use xxx.openhub.conf for illustration), but on content.
Correct configuration defined in jboss-deployment-structure.xml is expected (it is located in src/main/application/META-INF directory of maven module with ear packaging).
Note: for Jboss EAP 7, some public modules were added, like jackson, see https://access.redhat.com/articles/2158031 for full list.
JBoss module (module.xml file) can look like follow:
which has to be located in <JBOSS_HOME>/modules/xxx/openhub.conf directory. Content of this directory holds module descriptor itself and also another files which are expected to be on classpath, for example logback.xml (or similar logging SLF4J platform configuration), openhub.properties, quartz.properties and so on.
JBoss expects specific servlet path: in application.properties define server.servlet-path=/* (or via openhub.properties).
Datasource can be configured the standard way, and let openhub use jndi resource:
By default, jboss supplies transactionManager, which is autoconfigured by openhub. However in order to use it, spring jta must be disabled explicitely: