[jira] [Commented] (SYNCOPE-1262) Upgrade to Swagger UI 3.0
[ https://issues.apache.org/jira/browse/SYNCOPE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16363071#comment-16363071 ] ASF subversion and git services commented on SYNCOPE-1262: -- Commit 7958ebd48fadf04ad4b6d4f8a10507b6d5d078a0 in syncope's branch refs/heads/master from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=7958ebd ] [SYNCOPE-1262] Last matrix parameter still there > Upgrade to Swagger UI 3.0 > - > > Key: SYNCOPE-1262 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1262 > Project: Syncope > Issue Type: Task > Components: extensions >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.0.8, 2.1.0 > > > Since we introduced the support for Swagger (as an extension), I believe many > have found it very useful. > We are currently shipping a patched version of Swagger UI 2.0 (backed by > Swagger Core 1.5), with JS support manually enabled for Matrix parameters - > as such parameters are not officially supported by Swagger UI 2.0. > Luckily, after [long > discussions|https://github.com/OAI/OpenAPI-Specification/issues/69], it seems > that Matrix parameters eventually found their way through the OpenAPI > specification, and Swagger UI 3.0. > In order to profit from this, we need to generate an OpenAPI 3.0- compliant > descriptor, as the current /rest/swagger.json is at 2.0 but, due to the > presence of matrix parameters, doesn't load with Swagger UI 3.0. > There is an [ongoing effort in > CXF|https://issues.apache.org/jira/browse/CXF-7525] to provide full support > for OpenAPI 3.0, but the work has just started; moreover, this will only land > in CXF 3.2 - hence our branch {{2_0_X}} will not use it anyway. > Another approach, again provided by CXF, is the > [SwaggerToOpenApiConversionFilter|https://cwiki.apache.org/confluence/display/CXF20DOC/Swagger2Feature#Swagger2Feature-ConvertingtoOpenAPIJSON], > which is essentially an in-line transformer from the {{swagger.json}} we > already generate, to the new {{openapi.json}} in OpenAPI 3.0 format. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1262) Upgrade to Swagger UI 3.0
[ https://issues.apache.org/jira/browse/SYNCOPE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16363072#comment-16363072 ] ASF subversion and git services commented on SYNCOPE-1262: -- Commit 5cbdfe7bc58c37a026226b743d2ed9685ad19c37 in syncope's branch refs/heads/master from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=5cbdfe7 ] [SYNCOPE-1262] Last matrix parameter still there > Upgrade to Swagger UI 3.0 > - > > Key: SYNCOPE-1262 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1262 > Project: Syncope > Issue Type: Task > Components: extensions >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.0.8, 2.1.0 > > > Since we introduced the support for Swagger (as an extension), I believe many > have found it very useful. > We are currently shipping a patched version of Swagger UI 2.0 (backed by > Swagger Core 1.5), with JS support manually enabled for Matrix parameters - > as such parameters are not officially supported by Swagger UI 2.0. > Luckily, after [long > discussions|https://github.com/OAI/OpenAPI-Specification/issues/69], it seems > that Matrix parameters eventually found their way through the OpenAPI > specification, and Swagger UI 3.0. > In order to profit from this, we need to generate an OpenAPI 3.0- compliant > descriptor, as the current /rest/swagger.json is at 2.0 but, due to the > presence of matrix parameters, doesn't load with Swagger UI 3.0. > There is an [ongoing effort in > CXF|https://issues.apache.org/jira/browse/CXF-7525] to provide full support > for OpenAPI 3.0, but the work has just started; moreover, this will only land > in CXF 3.2 - hence our branch {{2_0_X}} will not use it anyway. > Another approach, again provided by CXF, is the > [SwaggerToOpenApiConversionFilter|https://cwiki.apache.org/confluence/display/CXF20DOC/Swagger2Feature#Swagger2Feature-ConvertingtoOpenAPIJSON], > which is essentially an in-line transformer from the {{swagger.json}} we > already generate, to the new {{openapi.json}} in OpenAPI 3.0 format. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1262) Upgrade to Swagger UI 3.0
[ https://issues.apache.org/jira/browse/SYNCOPE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16363070#comment-16363070 ] ASF subversion and git services commented on SYNCOPE-1262: -- Commit f154083938cf76e2f0835573c2c1a7d4614bcff5 in syncope's branch refs/heads/2_0_X from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=f154083 ] [SYNCOPE-1262] Last matrix parameter still there > Upgrade to Swagger UI 3.0 > - > > Key: SYNCOPE-1262 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1262 > Project: Syncope > Issue Type: Task > Components: extensions >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.0.8, 2.1.0 > > > Since we introduced the support for Swagger (as an extension), I believe many > have found it very useful. > We are currently shipping a patched version of Swagger UI 2.0 (backed by > Swagger Core 1.5), with JS support manually enabled for Matrix parameters - > as such parameters are not officially supported by Swagger UI 2.0. > Luckily, after [long > discussions|https://github.com/OAI/OpenAPI-Specification/issues/69], it seems > that Matrix parameters eventually found their way through the OpenAPI > specification, and Swagger UI 3.0. > In order to profit from this, we need to generate an OpenAPI 3.0- compliant > descriptor, as the current /rest/swagger.json is at 2.0 but, due to the > presence of matrix parameters, doesn't load with Swagger UI 3.0. > There is an [ongoing effort in > CXF|https://issues.apache.org/jira/browse/CXF-7525] to provide full support > for OpenAPI 3.0, but the work has just started; moreover, this will only land > in CXF 3.2 - hence our branch {{2_0_X}} will not use it anyway. > Another approach, again provided by CXF, is the > [SwaggerToOpenApiConversionFilter|https://cwiki.apache.org/confluence/display/CXF20DOC/Swagger2Feature#Swagger2Feature-ConvertingtoOpenAPIJSON], > which is essentially an in-line transformer from the {{swagger.json}} we > already generate, to the new {{openapi.json}} in OpenAPI 3.0 format. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1262) Upgrade to Swagger UI 3.0
[ https://issues.apache.org/jira/browse/SYNCOPE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16362554#comment-16362554 ] ASF subversion and git services commented on SYNCOPE-1262: -- Commit eb1cd3ff22d099c3c4978f56d104433f5bc23f31 in syncope's branch refs/heads/master from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=eb1cd3f ] [SYNCOPE-1262] Remove matrix parameters - OpenApi wins :-( > Upgrade to Swagger UI 3.0 > - > > Key: SYNCOPE-1262 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1262 > Project: Syncope > Issue Type: Task > Components: extensions >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.0.8, 2.1.0 > > > Since we introduced the support for Swagger (as an extension), I believe many > have found it very useful. > We are currently shipping a patched version of Swagger UI 2.0 (backed by > Swagger Core 1.5), with JS support manually enabled for Matrix parameters - > as such parameters are not officially supported by Swagger UI 2.0. > Luckily, after [long > discussions|https://github.com/OAI/OpenAPI-Specification/issues/69], it seems > that Matrix parameters eventually found their way through the OpenAPI > specification, and Swagger UI 3.0. > In order to profit from this, we need to generate an OpenAPI 3.0- compliant > descriptor, as the current /rest/swagger.json is at 2.0 but, due to the > presence of matrix parameters, doesn't load with Swagger UI 3.0. > There is an [ongoing effort in > CXF|https://issues.apache.org/jira/browse/CXF-7525] to provide full support > for OpenAPI 3.0, but the work has just started; moreover, this will only land > in CXF 3.2 - hence our branch {{2_0_X}} will not use it anyway. > Another approach, again provided by CXF, is the > [SwaggerToOpenApiConversionFilter|https://cwiki.apache.org/confluence/display/CXF20DOC/Swagger2Feature#Swagger2Feature-ConvertingtoOpenAPIJSON], > which is essentially an in-line transformer from the {{swagger.json}} we > already generate, to the new {{openapi.json}} in OpenAPI 3.0 format. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1262) Upgrade to Swagger UI 3.0
[ https://issues.apache.org/jira/browse/SYNCOPE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16362553#comment-16362553 ] ASF subversion and git services commented on SYNCOPE-1262: -- Commit b0b0e3294dd893d44845295f6a0f570d33fcc607 in syncope's branch refs/heads/master from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=b0b0e32 ] [SYNCOPE-1262] Adapting test to OpenAPI > Upgrade to Swagger UI 3.0 > - > > Key: SYNCOPE-1262 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1262 > Project: Syncope > Issue Type: Task > Components: extensions >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.0.8, 2.1.0 > > > Since we introduced the support for Swagger (as an extension), I believe many > have found it very useful. > We are currently shipping a patched version of Swagger UI 2.0 (backed by > Swagger Core 1.5), with JS support manually enabled for Matrix parameters - > as such parameters are not officially supported by Swagger UI 2.0. > Luckily, after [long > discussions|https://github.com/OAI/OpenAPI-Specification/issues/69], it seems > that Matrix parameters eventually found their way through the OpenAPI > specification, and Swagger UI 3.0. > In order to profit from this, we need to generate an OpenAPI 3.0- compliant > descriptor, as the current /rest/swagger.json is at 2.0 but, due to the > presence of matrix parameters, doesn't load with Swagger UI 3.0. > There is an [ongoing effort in > CXF|https://issues.apache.org/jira/browse/CXF-7525] to provide full support > for OpenAPI 3.0, but the work has just started; moreover, this will only land > in CXF 3.2 - hence our branch {{2_0_X}} will not use it anyway. > Another approach, again provided by CXF, is the > [SwaggerToOpenApiConversionFilter|https://cwiki.apache.org/confluence/display/CXF20DOC/Swagger2Feature#Swagger2Feature-ConvertingtoOpenAPIJSON], > which is essentially an in-line transformer from the {{swagger.json}} we > already generate, to the new {{openapi.json}} in OpenAPI 3.0 format. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1262) Upgrade to Swagger UI 3.0
[ https://issues.apache.org/jira/browse/SYNCOPE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16362318#comment-16362318 ] ASF subversion and git services commented on SYNCOPE-1262: -- Commit 6bc2cac1683aea747dcf02ca6ed31340088f9a33 in syncope's branch refs/heads/2_0_X from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=6bc2cac ] [SYNCOPE-1262] Remove matrix parameters - OpenApi wins :-( > Upgrade to Swagger UI 3.0 > - > > Key: SYNCOPE-1262 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1262 > Project: Syncope > Issue Type: Task > Components: extensions >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.0.8, 2.1.0 > > > Since we introduced the support for Swagger (as an extension), I believe many > have found it very useful. > We are currently shipping a patched version of Swagger UI 2.0 (backed by > Swagger Core 1.5), with JS support manually enabled for Matrix parameters - > as such parameters are not officially supported by Swagger UI 2.0. > Luckily, after [long > discussions|https://github.com/OAI/OpenAPI-Specification/issues/69], it seems > that Matrix parameters eventually found their way through the OpenAPI > specification, and Swagger UI 3.0. > In order to profit from this, we need to generate an OpenAPI 3.0- compliant > descriptor, as the current /rest/swagger.json is at 2.0 but, due to the > presence of matrix parameters, doesn't load with Swagger UI 3.0. > There is an [ongoing effort in > CXF|https://issues.apache.org/jira/browse/CXF-7525] to provide full support > for OpenAPI 3.0, but the work has just started; moreover, this will only land > in CXF 3.2 - hence our branch {{2_0_X}} will not use it anyway. > Another approach, again provided by CXF, is the > [SwaggerToOpenApiConversionFilter|https://cwiki.apache.org/confluence/display/CXF20DOC/Swagger2Feature#Swagger2Feature-ConvertingtoOpenAPIJSON], > which is essentially an in-line transformer from the {{swagger.json}} we > already generate, to the new {{openapi.json}} in OpenAPI 3.0 format. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1262) Upgrade to Swagger UI 3.0
[ https://issues.apache.org/jira/browse/SYNCOPE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16341023#comment-16341023 ] ASF subversion and git services commented on SYNCOPE-1262: -- Commit 28425614ebaee25e1235923e1a0dbff2ea88d83c in syncope's branch refs/heads/2_0_X from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=2842561 ] [SYNCOPE-1262] Adding authorizations > Upgrade to Swagger UI 3.0 > - > > Key: SYNCOPE-1262 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1262 > Project: Syncope > Issue Type: Task > Components: extensions >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.0.8, 2.1.0 > > > Since we introduced the support for Swagger (as an extension), I believe many > have found it very useful. > We are currently shipping a patched version of Swagger UI 2.0 (backed by > Swagger Core 1.5), with JS support manually enabled for Matrix parameters - > as such parameters are not officially supported by Swagger UI 2.0. > Luckily, after [long > discussions|https://github.com/OAI/OpenAPI-Specification/issues/69], it seems > that Matrix parameters eventually found their way through the OpenAPI > specification, and Swagger UI 3.0. > In order to profit from this, we need to generate an OpenAPI 3.0- compliant > descriptor, as the current /rest/swagger.json is at 2.0 but, due to the > presence of matrix parameters, doesn't load with Swagger UI 3.0. > There is an [ongoing effort in > CXF|https://issues.apache.org/jira/browse/CXF-7525] to provide full support > for OpenAPI 3.0, but the work has just started; moreover, this will only land > in CXF 3.2 - hence our branch {{2_0_X}} will not use it anyway. > Another approach, again provided by CXF, is the > [SwaggerToOpenApiConversionFilter|https://cwiki.apache.org/confluence/display/CXF20DOC/Swagger2Feature#Swagger2Feature-ConvertingtoOpenAPIJSON], > which is essentially an in-line transformer from the {{swagger.json}} we > already generate, to the new {{openapi.json}} in OpenAPI 3.0 format. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1262) Upgrade to Swagger UI 3.0
[ https://issues.apache.org/jira/browse/SYNCOPE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16341024#comment-16341024 ] ASF subversion and git services commented on SYNCOPE-1262: -- Commit 48cc9d6acda6bc28fdfca1a73a3d4f8df2e4460a in syncope's branch refs/heads/master from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=48cc9d6 ] [SYNCOPE-1262] Adding authorizations > Upgrade to Swagger UI 3.0 > - > > Key: SYNCOPE-1262 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1262 > Project: Syncope > Issue Type: Task > Components: extensions >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.0.8, 2.1.0 > > > Since we introduced the support for Swagger (as an extension), I believe many > have found it very useful. > We are currently shipping a patched version of Swagger UI 2.0 (backed by > Swagger Core 1.5), with JS support manually enabled for Matrix parameters - > as such parameters are not officially supported by Swagger UI 2.0. > Luckily, after [long > discussions|https://github.com/OAI/OpenAPI-Specification/issues/69], it seems > that Matrix parameters eventually found their way through the OpenAPI > specification, and Swagger UI 3.0. > In order to profit from this, we need to generate an OpenAPI 3.0- compliant > descriptor, as the current /rest/swagger.json is at 2.0 but, due to the > presence of matrix parameters, doesn't load with Swagger UI 3.0. > There is an [ongoing effort in > CXF|https://issues.apache.org/jira/browse/CXF-7525] to provide full support > for OpenAPI 3.0, but the work has just started; moreover, this will only land > in CXF 3.2 - hence our branch {{2_0_X}} will not use it anyway. > Another approach, again provided by CXF, is the > [SwaggerToOpenApiConversionFilter|https://cwiki.apache.org/confluence/display/CXF20DOC/Swagger2Feature#Swagger2Feature-ConvertingtoOpenAPIJSON], > which is essentially an in-line transformer from the {{swagger.json}} we > already generate, to the new {{openapi.json}} in OpenAPI 3.0 format. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1262) Upgrade to Swagger UI 3.0
[ https://issues.apache.org/jira/browse/SYNCOPE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16338887#comment-16338887 ] ASF subversion and git services commented on SYNCOPE-1262: -- Commit 046c354bd61f9889d7e59b71e0fe550d428e6ed3 in syncope's branch refs/heads/master from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=046c354 ] [SYNCOPE-1262] Since the proposed https://github.com/swagger-api/swagger-js/pull/1218 could not get accepted, let's go back to local patch for Swagger UI > Upgrade to Swagger UI 3.0 > - > > Key: SYNCOPE-1262 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1262 > Project: Syncope > Issue Type: Task > Components: extensions >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.0.8, 2.1.0 > > > Since we introduced the support for Swagger (as an extension), I believe many > have found it very useful. > We are currently shipping a patched version of Swagger UI 2.0 (backed by > Swagger Core 1.5), with JS support manually enabled for Matrix parameters - > as such parameters are not officially supported by Swagger UI 2.0. > Luckily, after [long > discussions|https://github.com/OAI/OpenAPI-Specification/issues/69], it seems > that Matrix parameters eventually found their way through the OpenAPI > specification, and Swagger UI 3.0. > In order to profit from this, we need to generate an OpenAPI 3.0- compliant > descriptor, as the current /rest/swagger.json is at 2.0 but, due to the > presence of matrix parameters, doesn't load with Swagger UI 3.0. > There is an [ongoing effort in > CXF|https://issues.apache.org/jira/browse/CXF-7525] to provide full support > for OpenAPI 3.0, but the work has just started; moreover, this will only land > in CXF 3.2 - hence our branch {{2_0_X}} will not use it anyway. > Another approach, again provided by CXF, is the > [SwaggerToOpenApiConversionFilter|https://cwiki.apache.org/confluence/display/CXF20DOC/Swagger2Feature#Swagger2Feature-ConvertingtoOpenAPIJSON], > which is essentially an in-line transformer from the {{swagger.json}} we > already generate, to the new {{openapi.json}} in OpenAPI 3.0 format. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1262) Upgrade to Swagger UI 3.0
[ https://issues.apache.org/jira/browse/SYNCOPE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16338886#comment-16338886 ] ASF subversion and git services commented on SYNCOPE-1262: -- Commit 400927ef055ce43c8cdc5a11c65a2cf5ee4dc0b5 in syncope's branch refs/heads/2_0_X from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=400927e ] [SYNCOPE-1262] Since the proposed https://github.com/swagger-api/swagger-js/pull/1218 could not get accepted, let's go back to local patch for Swagger UI > Upgrade to Swagger UI 3.0 > - > > Key: SYNCOPE-1262 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1262 > Project: Syncope > Issue Type: Task > Components: extensions >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.0.8, 2.1.0 > > > Since we introduced the support for Swagger (as an extension), I believe many > have found it very useful. > We are currently shipping a patched version of Swagger UI 2.0 (backed by > Swagger Core 1.5), with JS support manually enabled for Matrix parameters - > as such parameters are not officially supported by Swagger UI 2.0. > Luckily, after [long > discussions|https://github.com/OAI/OpenAPI-Specification/issues/69], it seems > that Matrix parameters eventually found their way through the OpenAPI > specification, and Swagger UI 3.0. > In order to profit from this, we need to generate an OpenAPI 3.0- compliant > descriptor, as the current /rest/swagger.json is at 2.0 but, due to the > presence of matrix parameters, doesn't load with Swagger UI 3.0. > There is an [ongoing effort in > CXF|https://issues.apache.org/jira/browse/CXF-7525] to provide full support > for OpenAPI 3.0, but the work has just started; moreover, this will only land > in CXF 3.2 - hence our branch {{2_0_X}} will not use it anyway. > Another approach, again provided by CXF, is the > [SwaggerToOpenApiConversionFilter|https://cwiki.apache.org/confluence/display/CXF20DOC/Swagger2Feature#Swagger2Feature-ConvertingtoOpenAPIJSON], > which is essentially an in-line transformer from the {{swagger.json}} we > already generate, to the new {{openapi.json}} in OpenAPI 3.0 format. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1262) Upgrade to Swagger UI 3.0
[ https://issues.apache.org/jira/browse/SYNCOPE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316295#comment-16316295 ] ASF subversion and git services commented on SYNCOPE-1262: -- Commit 1d5d31cc83c0d9afefc18cb7c9864170cc69f0c7 in syncope's branch refs/heads/2_0_X from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=1d5d31c ] [SYNCOPE-1262] Looks better > Upgrade to Swagger UI 3.0 > - > > Key: SYNCOPE-1262 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1262 > Project: Syncope > Issue Type: Task > Components: extensions >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Fix For: 2.0.8, 2.1.0 > > > Since we introduced the support for Swagger (as an extension), I believe many > have found it very useful. > We are currently shipping a patched version of Swagger UI 2.0 (backed by > Swagger Core 1.5), with JS support manually enabled for Matrix parameters - > as such parameters are not officially supported by Swagger UI 2.0. > Luckily, after [long > discussions|https://github.com/OAI/OpenAPI-Specification/issues/69], it seems > that Matrix parameters eventually found their way through the OpenAPI > specification, and Swagger UI 3.0. > In order to profit from this, we need to generate an OpenAPI 3.0- compliant > descriptor, as the current /rest/swagger.json is at 2.0 but, due to the > presence of matrix parameters, doesn't load with Swagger UI 3.0. > There is an [ongoing effort in > CXF|https://issues.apache.org/jira/browse/CXF-7525] to provide full support > for OpenAPI 3.0, but the work has just started; moreover, this will only land > in CXF 3.2 - hence our branch {{2_0_X}} will not use it anyway. > Another approach, again provided by CXF, is the > [SwaggerToOpenApiConversionFilter|https://cwiki.apache.org/confluence/display/CXF20DOC/Swagger2Feature#Swagger2Feature-ConvertingtoOpenAPIJSON], > which is essentially an in-line transformer from the {{swagger.json}} we > already generate, to the new {{openapi.json}} in OpenAPI 3.0 format. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SYNCOPE-1262) Upgrade to Swagger UI 3.0
[ https://issues.apache.org/jira/browse/SYNCOPE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312942#comment-16312942 ] ASF subversion and git services commented on SYNCOPE-1262: -- Commit a8dd6b794e85488e2281de4a2027d727fcdbd061 in syncope's branch refs/heads/master from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=a8dd6b7 ] [SYNCOPE-1262] Taking the SwaggerToOpenApiConversionFilter approach > Upgrade to Swagger UI 3.0 > - > > Key: SYNCOPE-1262 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1262 > Project: Syncope > Issue Type: Task > Components: extensions >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Fix For: 2.0.8, 2.1.0 > > > Since we introduced the support for Swagger (as an extension), I believe many > have found it very useful. > We are currently shipping a patched version of Swagger UI 2.0 (backed by > Swagger Core 1.5), with JS support manually enabled for Matrix parameters - > as such parameters are not officially supported by Swagger UI 2.0. > Luckily, after [long > discussions|https://github.com/OAI/OpenAPI-Specification/issues/69], it seems > that Matrix parameters eventually found their way through the OpenAPI > specification, and Swagger UI 3.0. > In order to profit from this, we need to generate an OpenAPI 3.0- compliant > descriptor, as the current /rest/swagger.json is at 2.0 but, due to the > presence of matrix parameters, doesn't load with Swagger UI 3.0. > There is an [ongoing effort in > CXF|https://issues.apache.org/jira/browse/CXF-7525] to provide full support > for OpenAPI 3.0, but the work has just started; moreover, this will only land > in CXF 3.2 - hence our branch {{2_0_X}} will not use it anyway. > Another approach, again provided by CXF, is the > [SwaggerToOpenApiConversionFilter|https://cwiki.apache.org/confluence/display/CXF20DOC/Swagger2Feature#Swagger2Feature-ConvertingtoOpenAPIJSON], > which is essentially an in-line transformer from the {{swagger.json}} we > already generate, to the new {{openapi.json}} in OpenAPI 3.0 format. -- This message was sent by Atlassian JIRA (v6.4.14#64029)