[
https://issues.apache.org/jira/browse/CXF-7525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16287438#comment-16287438
]
Sergey Beryozkin commented on CXF-7525:
---------------------------------------
Hi Andriy, sure, reusing the code is a very good idea, I was ignorant about the
fact UI 3.5.0 is capable of working with both swagger.json and openapi.json,
and was temp confused with some of the refactoring changes, it looks nice and
is indeed needed with the intro of open api feature, thanks
Re injecting the provider, the idea occurred to me after we could not agree for
a while with Christian how to deal with the OSGi resolution, so I thought,
rather than trying to come up with the built in universal solution, it would be
good to let users do "feature.setSwaggerUiResolver(new MyResolver())" - and if
it is not set then the default resolution tales place. So "SwaggerUiResolver"
becomes an interface, and the current "SwaggerUiResolver" becomes the default
SwaggerUiResolverImpl (which will do what it does now - use non-OSGI or OSGI
resolution). See what I mean ?
By the way, is passing a classloader to the non-OSGI SwaggerUiResolver needed ?
May be getClass().getClassLoader() will do ?
Thanks
> Add support for Swagger 2.0 (OpenApi Spec 3.0)
> ----------------------------------------------
>
> Key: CXF-7525
> URL: https://issues.apache.org/jira/browse/CXF-7525
> Project: CXF
> Issue Type: Improvement
> Reporter: Andriy Redko
> Assignee: Andriy Redko
>
> The OpenApi spec 3.0 has been released recently. Swagger 2.0 (currently in
> rc-2) should released in a few months (Dec/Jan). It would be great to have
> the integration available in CXF as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
