[
https://issues.apache.org/jira/browse/CXF-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15981463#comment-15981463
]
Sergey Beryozkin commented on CXF-7347:
---------------------------------------
Peter, I've adjusted a bit the Pattern and now those root resources are picked
up (looks like so to me at least).
The problem which is still unresolved is how to tell UI 3 how to properly
handle a 'host' issue. I'm nearly 100% sure it is not correctly dealing with it
- it does understand in one place (just below a licence link) that a host
should be resolved to http://localhost:8080 (or similar), but in its Try Out it
fails to resolve it correctly, as well as in its Validate Model link.
I'd say a PR needs to be provided for UI 3 in order to make it work
consistently.
The only other alternative is to configure Swagger2Feature with the host and
port info which is not cool at all
> 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
>
> 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)
