There should be a mechanism to exclude a class or method from the /resourceList construction on a @controller that had been loaded from the ApiDocumentationController.
Currently, the ApiDocumentationController will process all the @controllers with @RequestMapping and there is a mechanism for excluding custom annotations (setIgnorableAnnotations()). This may not be easy to do when there is a 3rd party library where we would to generate Swagger for some controllers but exclude others.
The 'Filter' interface provide a mechanism to include/exclude specific methods but these filters are only used if there are no request mappings.
One possible solution could be to honor the same @ComponentScan/excludeFilters that Spring @configuration uses.
There should be a mechanism to exclude a class or method from the /resourceList construction on a @controller that had been loaded from the ApiDocumentationController.
Currently, the ApiDocumentationController will process all the @controllers with @RequestMapping and there is a mechanism for excluding custom annotations (setIgnorableAnnotations()). This may not be easy to do when there is a 3rd party library where we would to generate Swagger for some controllers but exclude others.
The 'Filter' interface provide a mechanism to include/exclude specific methods but these filters are only used if there are no request mappings.
One possible solution could be to honor the same @ComponentScan/excludeFilters that Spring @configuration uses.