1 of 1 people found this helpful
It seems when loading the filter the module service is not able to do so due to some class not avalable to the module class loader trying to loading it (the war).
The full stack trace should have the missing class. Then you have to identify the module in which it is and explisitly mark it as a depedencie in the jboss-structure-deployment.xml file.
If it is a Jax-rs class missing, they may have missing implicite depedencies.
If you want more detail, please provide fulll stack trace.
In the stacktrace I saw that it was complaining about the class javax.ws.rs.container.ContainerResponseFilter. But this is a class which is available on the container as it should be a EE compliant server.
If I add the following dependency to the war, it works
But as I said, this is wrong.
This is clearly a bug. You should fill in a bug report.