[
https://issues.apache.org/jira/browse/CXF-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984438#comment-15984438
]
Sergey Beryozkin commented on CXF-7347:
---------------------------------------
Peter, thanks for the update.
I'm not sure what you mean about sending a request to "localhost:8080".
In the Swagger2Feature to SwaggerUI autolinking node (which is where this
Pattern check is relevant) CXF creates a Swagge UI endpoint relative to a
JAX-RS endpoint address, a relative 'url' parameter one enters in the browser
is now supposed to be correctly interpreted by UI, it works fine in UI 2.x but
is not so in UI 3.0.
> Support Swagger UI 3
> --------------------
>
> Key: CXF-7347
> URL: https://issues.apache.org/jira/browse/CXF-7347
> 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
(v6.3.15#6346)
