Github user reta commented on the issue:
https://github.com/apache/cxf/pull/160
Hi Lukasz,
Thanks a lot for the patch. What would be a use case to use such precise
and not really straightforward Swagger configuration in CXF? I think the
approach with path-based configuration (which essentially does the same trick
by manipulating scanner/config ids) is simpler and does not really expose the
internals of Swagger to CXF users. Plus, we could just make it a default
behavior so the need to manipulate scanner/config ids would be a very rare
exception if at all.
What do you think?
Thank you.
Best Regards,
Andriy redko
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
