Configuration not applied after upgrading to 1.5.7

Hello,

I’m using jersey-core 1.5.5 and I need to upgrade to >= 1.5.7 in order to fix ObjectMapper issue #1604 (my JSON date formatting is incorrect).

It works fine but now I have a problem with the swagger.json, my configuration is not applied :

{"swagger":"2.0","info":{"version":"Swagger Server","title":""},"tags": ...

The rest of the document is correct, I can use it in Swagger-UI but I can’t call my API because host / basePath are not set in the document. My configuration is defined like in this post (to define contextPath as basePath) : http://stackoverflow.com/a/35905415/1001248

I’m using swagger-jersey-jaxrs in a Glassfish 3.1.2.2 environnement.

[fdelsert]

I understand.

I pushed a sample maven project to reproduce the issue : https://github.com/fdelsert/swagger-issue-1886

I excluded Jersey dependencies 1.13 of swagger-jersey-jaxrs because I use Jersey 1.11 provided by Glassfish server. Maybe the problem comes from an incompatibility with the Jersey version.

Direct links :

• pom.xml
• web.xml
• configuration servlet class
• endpoint

[fehguy]

OK, the BeanConfig is used for programmatic configuration without needing web.xml. The web.xml configuration will not trigger scanning in BeanConfig. So you have two choices:

1. Use web.xml through the DefaultJaxrsConfig. You don’t need to subclass it, and doing so the way you did isn’t going to work. Use the fields that are supported in that class, including host and basepath.

2. Use a programmatic configuration. You can follow a pattern like this:

https://github.com/swagger-api/swagger-samples/tree/master/java/java-jaxrs

Where a web.xml configures most of the application, and a custom servlet does the rest.