Status: Closed (View Workflow)
Affects Version/s: 2.3.3.Final
Steps to Reproduce:
Reproducer project is available from:
In step 3, instead of picking up the StringConverter in the second resource module, it fails.Reproducer project is available from: https://github.com/mattiasholmqvist/jboss-jaxrs-provider-test To reproduce: 1. Run: mvn clean install jboss-as:deploy 2. Go to http://localhost: <port>/first 3. Go to http://localhost: <port>/second/USD In step 3, instead of picking up the StringConverter in the second resource module, it fails.
It looks like it's possible to put all the @Provider-classes in the same module so that they all get picked up by the initialization. This is however not a viable option for us.
When using two applications (WARs) in the same JBoss, RestEASY only picks up the @Provider-classes for the application that gets initialized first.
I have a suggested fix for the issue at:
Where the CdiInjectorFactory uses the newly created InjectorFactory from the ResteasyProviderFactory (which is in turn created in ResteasyDeployment) instead of using getInstance() in the constructor. This fixes the issue in our setup.
If this looks reasonable to you I can create a pull request from the branch.
PS. I tried to create a discussion thread first but I couldn't get access to RestEasy discussion forums for some reason. DS.