As usual, Dmitry has the right answer.
What is interesting (annoying?) is that I was trying to do this per the
Wildfly docs with a "Dependencies" attribute in my JAR manifest. However,
that didn't work and I assumed that it was something deeper. I assumed
that if that didn't work that the jboss-deployment-structure.xml file
wouldn't be any different.
As always - Thanks to Dmitry for saving me!
Craig
=================================
*Craig Setera*
*Chief Technology Officer*
On Fri, Feb 1, 2019 at 4:51 PM Dmitry Telegin <dt(a)acutus.pro> wrote:
Hello Craig,
In JBoss/Wildfly environment, you need to explicitly declare runtime
dependencies. I assume that you're deploying your provider via dropping the
JAR into the standalone/deployments dir. In this case, you need to have
META-INF/jboss-deployment-structure.xml like this:
<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure>
<deployment>
<dependencies>
<module name="org.keycloak.keycloak-services" />
</dependencies>
</deployment>
</jboss-deployment-structure>
If you are deploying as a module, use "module add ...
--dependencies=org.keycloak.keycloak-services" jboss-cli command. It will
auto-create the proper XML module descriptor for you.
Cheers,
Dmitry