I’ve doubtless done something wrong, but the technique suggested above does not work. I placed the configurator jar file in this directory:
I then created a module.xml file with the following content:
<module xmlns="urn:jboss:module:1.0" name="com.att.gcs.bizops.cop.connector.GcsBpoCustomHttpConnectorConfigurator">
<resource-root path="GcsBpoCustomHttpConnectorConfigurator-0.0.1.jar" />
I then modified the both copies of the camunda-engine-plugin-connect module.xml file and added the following entry:
<module name="com.att.gcs.bizops.cop.connector.GcsBpoCustomHttpConnectorConfigurator" services="import" />
I restarted WildFly, ran a process, then checked the WildFly DEBUG level output for threads allocated, and it did not change from the default.
I have had very little luck getting WildFly to load modules, despite hours of trying for different modules. I’m not sure if this is a dependency issue that I needed to account for in the configurator module.xml file or not.
In any event, both methods involve modifying the base Camunda/WildFly distribution, so I suppose there’s little difference in terms of long-term maintenance.