[
https://issues.apache.org/jira/browse/CXF-7022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455232#comment-15455232
]
Sergey Beryozkin commented on CXF-7022:
---------------------------------------
Hi Francesco, FYI, I had to update the interface as part of this JIRA:
https://issues.apache.org/jira/browse/CXF-7035
By the way I start wondering if having an interface is a problem for the future
or not (I suggested it during our discussion :-)). We don't know what yet we
may need to make available on it. We can of course keep enhancing
DefaultSwagger2Serializers but it means other custom serializers will miss out
unless we update the interface.
Moving Swagger2Serilaizers code into its own class is def good but may be it
will be easier going forward simply to have Swagger2Serilaizers class and only
keep enhancing it ? (to support the extra headers, making BeanConfig as in case
of CXF-7035 visible to it, etc, etc)
> Allow customization of Swagger JSON generation
> ----------------------------------------------
>
> Key: CXF-7022
> URL: https://issues.apache.org/jira/browse/CXF-7022
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS
> Reporter: Francesco Chicchiriccò
> Assignee: Francesco Chicchiriccò
> Labels: swagger
> Fix For: 3.2.0, 3.1.8, 3.0.11
>
>
> Swagger JSON generation is currently performed in
> {{org.apache.cxf.jaxrs.swagger.Swagger2Serializers}}, which is directly
> instantiated by {{org.apache.cxf.jaxrs.swagger.Swagger2Feature}}.
> The latter can take a former's instance as parameter, thus allowing
> customization in a given deployment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
