Swagger-Jaxrs does not recognize @API annotations with different classloader

[tobiasvoelke]

I am using swagger-jaxrs (1.5.12) in a webservice which is contained in a war-file.
The webservice implementation and its contract is placed in the underlying ear file.

The classes are discovered by the Scanner (which as well checks for the annotation!) but the reader fails to recognize the Annotations. This seems to be caused by the fact that the swagger-annotation-jar classes are loaded with two different classloaders.

The jar is placed in the ear visible to all modules but, by definition ,Wildlfy uses a different classloader for every war (and the underlying ear).

I would expect the swagger-core to recognize the annotation either way. The deployment of the webservice endpoints is working without any problems.

For further Information see this stackoverflow-question

[dolejnik]

Possibly same problem as #485