You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
leading / are not required in Jersey annotations so you can have
@Path("foo")
class Foo {
@GET
public Response getFoo() {
}
@GET @Path("bar")
public Response getBar() {
}
which correctly handles the resource path /foo/bar
However, swagger forgets to include / in concatenations so this converts to 2 api sets - /foo and /foobar instead of /foo/bar. The only workaround I see is to use @get@path("/bar") which does create /foo/bar
Also note that swagger does properly prefix /foo in both basePath, resourcePath and apis/path values so this seems to only be a problem with sub-resources
The text was updated successfully, but these errors were encountered:
found in 1.3.10
leading / are not required in Jersey annotations so you can have
which correctly handles the resource path /foo/bar
However, swagger forgets to include / in concatenations so this converts to 2 api sets - /foo and /foobar instead of /foo/bar. The only workaround I see is to use @get @path("/bar") which does create /foo/bar
Also note that swagger does properly prefix /foo in both basePath, resourcePath and apis/path values so this seems to only be a problem with sub-resources
The text was updated successfully, but these errors were encountered: