[
https://issues.apache.org/jira/browse/CXF-7957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16756105#comment-16756105
]
James Carman commented on CXF-7957:
-----------------------------------
I figured out the issue. The Swagger folks decided to switch from manually
serializing their Swagger objects to JSON to using the SwaggerSerializers to
take care of it for them. One quick fix is to simply add SwaggerSerializers to
the "providers" list in the Swagger2Feature. However, the systest for
SwaggerToOpenApiConversionFilter fails, because
SwaggerToOpenApiConversionFilter assumes the entity returned is a String object
and casts it to String (it's a Swagger object). Working on the fix for that
now...
> Swagger2Feature Doesn't Work With Swagger Versions Above 1.5.17
> ---------------------------------------------------------------
>
> Key: CXF-7957
> URL: https://issues.apache.org/jira/browse/CXF-7957
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS, Services
> Affects Versions: 3.3.0
> Reporter: James Carman
> Assignee: Andriy Redko
> Priority: Major
>
> We were trying to bump up to the latest patch versions of all of our
> dependencies. When we upgrade Swagger to the latest version, it caused the
> Swagger UI to break and we noticed this message in the logs:
> "Problem with writing the data, class io.swagger.models.Swagger, ContentType:
> application/json"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
