From dev-return-14947-archive-asf-public=cust-asf.ponee.io@syncope.apache.org Fri Jan 5 11:44:04 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id C77F8180647 for ; Fri, 5 Jan 2018 11:44:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id B7FEA160C3B; Fri, 5 Jan 2018 10:44:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 0A01F160C27 for ; Fri, 5 Jan 2018 11:44:03 +0100 (CET) Received: (qmail 51618 invoked by uid 500); 5 Jan 2018 10:44:03 -0000 Mailing-List: contact dev-help@syncope.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@syncope.apache.org Delivered-To: mailing list dev@syncope.apache.org Received: (qmail 51607 invoked by uid 99); 5 Jan 2018 10:44:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Jan 2018 10:44:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id BA2A71A0AD3 for ; Fri, 5 Jan 2018 10:44:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.511 X-Spam-Level: X-Spam-Status: No, score=-99.511 tagged_above=-999 required=6.31 tests=[KAM_NUMSUBJECT=0.5, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id ytN-5R56deTK for ; Fri, 5 Jan 2018 10:44:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id A5DFE5FB02 for ; Fri, 5 Jan 2018 10:44:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 0CA84E256B for ; Fri, 5 Jan 2018 10:44:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 62FFD240FE for ; Fri, 5 Jan 2018 10:44:00 +0000 (UTC) Date: Fri, 5 Jan 2018 10:44:00 +0000 (UTC) From: =?utf-8?Q?Francesco_Chicchiricc=C3=B2_=28JIRA=29?= To: dev@syncope.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (SYNCOPE-1262) Upgrade to Swagger UI 3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Francesco Chicchiricc=C3=B2 created SYNCOPE-1262: ----------------------------------------------- Summary: 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=C3=B2 Assignee: Francesco Chicchiricc=C3=B2 Fix For: 2.0.8, 2.1.0 Since we introduced the support for Swagger (as an extension), I believe ma= ny have found it very useful. We are currently shipping a patched version of Swagger UI 2.0 (backed by Sw= agger Core 1.5), with JS support manually enabled for Matrix parameters - a= s such parameters are not officially supported by Swagger UI 2.0. Luckily, after [long discussions|https://github.com/OAI/OpenAPI-Specificati= on/issues/69], it seems that Matrix parameters eventually found their way t= hrough 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 pr= esence of matrix parameters, doesn't load with Swagger UI 3.0. There is an [ongoing effort in CXF|https://issues.apache.org/jira/browse/CX= F-7525] to provide full support for OpenAPI 3.0, but the work has just star= ted; 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 [SwaggerToOpenApiConversion= Filter|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 {{ope= napi.json}} in OpenAPI 3.0 format. -- This message was sent by Atlassian JIRA (v6.4.14#64029)