[
https://issues.apache.org/jira/browse/CXF-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984531#comment-15984531
]
Sergey Beryozkin edited comment on CXF-7347 at 4/26/17 10:16 AM:
-----------------------------------------------------------------
Peter, thanks, FYI, in my case 'Base url' does not even show the host and port
values only the relative bits, you are probably using the early UI 3.0.0 ?
2 days back, while testing with UI 3.0.5, I updated the CXF code to auto-set
the host value because UI 3.0.5 could not do Try Out. Dennis reported that UI
3.0.7 was out so I removed that CXF auto-set host code and tried it this
morning with UI 3.0.7 and TryOut works OK.
I can only imagine that perhaps the code I did might be affecting this
localhost vs 127.0.0.1 issue you are seeing.
I've just redeployed cxf-rt-rs-description-swagger in 3.0.12-SNAPSHOT, can you
try it please with UI 3.0.7 ?
If you are still seeing this issue then please take it to the Swagger UI 3 team.
I think as far as CXF is concerned we are now ready to resolve this issue.
Also, FYI, I've opened
https://github.com/swagger-api/swagger-ui/issues/2978
was (Author: sergey_beryozkin):
Peter, thanks, FYI, in my case 'Base url' does not even show the host and port
values only the relative bits, you are probably using the early UI 3.0.0 ?
2 days back, while testing with UI 3.0.5, I updated the CXF code to auto-set
the host value because UI 3.0.5 could not do Try Out. Dennis reported that UI
3.0.7 was out so I removed that CXF auto-set host code and tried it this
morning with UI 3.0.7 and TryOut works OK.
I can only imagine that perhaps the code I did might be affecting this
localhost vs 127.0.0.1 issue you are seeing.
I've just redeployed cfg-rt-rs-description-swagger in 3.0.12-SNAPSHOT, can you
try it please with UI 3.0.7 ?
If you are still seeing this issue then please take it to the Swagger UI 3 team.
I think as far as CXF is concerned we are now ready to resolve this issue.
Also, FYI, I've opened
https://github.com/swagger-api/swagger-ui/issues/2978
> 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-basepath-127001.PNG,
> swagger-ui-basepath-localhost.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)
