Hi Sergey! > I guess the feature would check the properties at the configurable > 'swaggerPropertiesLocation', with "/swagger.properties" being the > default one, and then use them to set the simple Swagger properties > which has not been already set by SwaggerFeature setters ?
Yes, this makes sense, good idea. > > The other thing which is worth investigating is having SwaggerFeature > > checking if swagger.json is already available on the class path (done > > earlier by java2swagger) and if yes then do not register Swagger > > ApiListing at all and register instead a simple resource (similar to the > > UI one) which will serve this swagger.json > > Similarly, it would probably check for a /swagger.json resource with the > location being configurable, and if avail - then skip all that code > which registers ApiListing, etc, though may be it will become a bit too > messy, may be we should start with the above task first > > Freeman - how do you serve those generated swagger.jsons, is it detected > by ApiListing or do you register some custom resource ? This is definitely an improvement for API-First development. Currently I have tests in place to ensure the generated swagger.json matches the manually defined one. Cheers Dennis
