cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter van den Broek (JIRA)" <>
Subject [jira] [Commented] (CXF-7347) Support Swagger UI 3
Date Wed, 26 Apr 2017 09:11:04 GMT


Peter van den Broek commented on CXF-7347:

Sergey, thanks for the quick fix.

The problem with the CSS and such seems te be resolved.
I've tested the change and have been seeing this host issue you've mentioned.

Visiting the Swagger UI via causes the requests to be sent to localhost:8080
(which fails).
This happens in both Swagger UI 2 and 3, when using CXF 3.1.12-SNAPSHOT version.
It doesn't happen in 3.1.11 (for Swagger UI 2, UI 3 is just not resolving the host at all
and tries to send messages to http://:8080)

I could not replicate the error mentioned by Dennis, but I have seen this in the past for
very complex swagger.json files.
It might be more related to Swagger itself than to the CXF implementation.

> Support Swagger UI 3
> --------------------
>                 Key: CXF-7347
>                 URL:
>             Project: CXF
>          Issue Type: New Feature
>            Reporter: Peter van den Broek
>            Assignee: Sergey Beryozkin
>         Attachments: swagger3.png
> Swagger UI 3.0.0 was released on 18 March 2017 and brings a full rewrite of the UI from
the ground up.
> In this version, they've changed the directory structure to being flat with only a couple
of files left.
> This means the CSS and JS files are now located in the root of the folder and most files
have been merged or removed.
> Swagger2Feature contains an internal SwaggerUIResourceFilter that checks for files in
these (no longer existing) subfolders, but does not find the new location of (for example)
css files.
> The pattern it uses is:
> {code}
> .*[.]js|/css/.*|/images/.*|/lib/.*|.*ico|/fonts/.*
> {code}
> This no longer works, since it doesn't allow for files (other than JS and ICO) to be
in the root folder.

This message was sent by Atlassian JIRA

View raw message