Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Thu, 1 Sep 2016 12:30:21 +0000 (UTC)
From: "Sergey Beryozkin (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12999639.1472039305000.468581.1472733021686@Atlassian.JIRA>
In-Reply-To: <JIRA.12999639.1472039305000@Atlassian.JIRA>
References: <JIRA.12999639.1472039305000@Atlassian.JIRA> <JIRA.12999639.1472039305774@arcas>
Subject: [jira] [Comment Edited] (CXF-7022) Allow customization of Swagger
 JSON generation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Thu, 01 Sep 2016 12:30:23 -0000


    [ https://issues.apache.org/jira/browse/CXF-7022?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D154552=
32#comment-15455232 ]=20

Sergey Beryozkin edited comment on CXF-7022 at 9/1/16 12:30 PM:
----------------------------------------------------------------

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 fu=
ture 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 De=
faultSwagger2Serializers but it means other custom serializers will miss ou=
t unless we update the interface.=20

Moving Swagger2Serilaizers code into its own class is def good but may be i=
t 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)
For example, right now a default one is missing the extra headers support w=
hich can be of general interest=20


was (Author: sergey_beryozkin):
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 fu=
ture 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 De=
faultSwagger2Serializers but it means other custom serializers will miss ou=
t unless we update the interface.=20
Moving Swagger2Serilaizers code into its own class is def good but may be i=
t 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=C3=B2
>            Assignee: Francesco Chicchiricc=C3=B2
>              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.apac=
he.cxf.jaxrs.swagger.Swagger2Feature}}.
> The latter can take a former's instance as parameter, thus allowing custo=
mization in a given deployment.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)