Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
tobiasvoelke opened this issue May 5, 2017 · 1 comment

Comments

@tobiasvoelke
Copy link

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
Copy link

dolejnik commented Jul 5, 2017

Possibly same problem as #485

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants