-
Notifications
You must be signed in to change notification settings - Fork 261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Swagger API docs not rendering #7543
Comments
Following some fixes as part of fixing #7424
, the new behaviour is
HOWEVER, the api endpoint is not available
Note the 'ClassCastException' |
|
This technically recomments requiring
presumably at implementation Scope. However this causes a dependency warning
But both versions cause the same error in the browser - and inability to get to /v3/api-docs |
Checking dependency chains. On the server chassis:
But then the actual spring starter wants the non jarkarta version:
Whilst one of these is needed (we only need the annotations to compile -- whilst does work if the entire springdoc webmvc starter is pulled in, it's unnecessary for compile, and breaks our validation rules) - with both behaving the same, will leave the code with the preferred version here included. |
Signed-off-by: Nigel Jones <[email protected]>
@bogdan-sava any ideas here? |
indeed |
Thanks @planetf1 |
Thanks @bogdan-sava - that addresses the security issue with the ui -- and swagger now works fine there There remains an issue with the core chassis - I'll take another look (your thoughts welcome!) to see if I can identify the discrepancy which is causing a 500 on getting the API definition. It's likely dependency related -- the main chassis has a lot more components by default. |
Confirmed, tests ok in main. Thanks for fixing |
Unable to use swagger API with ui chassis:
Possibly permission related
http -a admin:secret --follow --verify=false GET https://localhost:8443/swagger-ui.html
has the same result
meantime .. The server chassis itself does not have swagger at all - the swagger page does not exist
The text was updated successfully, but these errors were encountered: