[
https://issues.apache.org/jira/browse/CXF-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004443#comment-16004443
]
Sergey Beryozkin commented on CXF-7316:
---------------------------------------
OK, I've committed the following:
http://git-wip-us.apache.org/repos/asf/cxf/commit/e490f5c8
I haven't updated the actual swagger-jaxrs version as it will not work in OSGI
as we already know and if we do upgrade then suddenly the code which depends on
the DefaultSwagger2Serializers being called will stop working which we also
already know.
What I did I introduced Swagger2Customizer and moved most of
DefaultSwagger2Serializers into it.
[~ilgrosso] Hi Francesco - a bit of a problem here for Syncope
DefaultSwagger2Serializers extension because all the customization code is now
in Swagger2Customizer - so you'd extend it instead and set on
DefaultSwagger2Serializers while you still work with swagger-jaxrs 1.5.12.
Unfortunately, it looks like that the time has come to move away from depending
on DefaultSwagger2Serializers in order to get Swagger instance customized.
We will just need to remove it as soon as we migrate to swagger 1.5.13 because
it will not be effective from then on.
Dennis, Francesco, can you please try the latest 3.1.x code and confirm it
works OK for you with 1) swagger-jaxrs 1.5.12 (default) and 2) with
swagger-jaxrs 1.5.13 - update the deps and make sure you do "Swagger2Feature
feature = new Swagger2Feature(); feature.setCustomizer(new
Swagger2Customizer);" to get 1.5.13-compliant mode of operation activated
thanks
> Update swagger-jaxrs dependency to 1.5.13
> -----------------------------------------
>
> Key: CXF-7316
> URL: https://issues.apache.org/jira/browse/CXF-7316
> Project: CXF
> Issue Type: Task
> Affects Versions: 3.1.10
> Reporter: Dennis Kieselhorst
> Priority: Minor
> Fix For: 3.2.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
