-
Notifications
You must be signed in to change notification settings - Fork 493
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
OpenAPI endpoint is broken #9981
Comments
Thanks for discussing this and opening this OpenAPI/Swagger issue, @JR-1991! I showed the stacktrace below (from my laptop running 7e0738e, the latest from the develop branch) to @poikilotherm and he found what seems to be a related issue on the Payara side: @donsizemore found this issue: Here's the stacktrace: openapi-error.txt Other open Swagger/OpenAPI issues: |
Today @poikilotherm suggested using https://github.com/OpenAPITools/openapi-generator which would not be dependent on Payara (should also work if we switched to Wildfly or OpenLiberty, etc.). Also, it doesn't require the app server to be running. |
2024/01/08: Prioritized and moved to Needs Sizing during prioritization meeting. |
2024/01/08: Moved to Needs Sizing during today's prioritization meeting |
As discussed yesterday at tech hours, a simple thing is to ask Payara about how the fix is coming along. I just did this in payara/Payara#6369 (comment) As switching to output generated from https://github.com/OpenAPITools/openapi-generator none of us have tried that library and we don't have a great sense of how much effort it is. A major use case for getting |
2024/01/16: Recommendation to create a separate spike (10) to investigate the tool suggested here: #9981 (comment) |
2024/01/16: spike created: #10236 |
2024/01/16: Moved to waiting. Work will continue via #10236 while we wait for response from Payara. |
This just in. Someone has come up with a potential fix for Payara: |
I just built that PR with this:
Then I uploaded it to Google Drive: https://drive.google.com/file/d/17kVKOco86FDKXvs1aBZLq9QBABxO8S5A/view?usp=drive_link I haven't tested it to see if /openapi works or not. |
2024/03/14
|
This PR was just closed as already fixed. See: |
Payara 6.2024.4 RC1 is just in today. I suppose there will be a new release soon. We should update our version of Payara as it also contains my MPC NPE fix. We can check back again if it started working again. |
If this is the case we should probably have to decide what to do with #10328 here are a few things to consider:
|
* Plugin initial config * Initial changes to provide OpenAPI definition * Added integration test * Imports fix * Add patchnotes * Update the changelog * Update src/main/java/edu/harvard/iq/dataverse/api/Info.java Co-authored-by: Philip Durbin <[email protected]> * Update doc/release-notes/10236-openapi-definition-endpoint.md Co-authored-by: Philip Durbin <[email protected]> * Update doc/release-notes/10236-openapi-definition-endpoint.md Co-authored-by: Philip Durbin <[email protected]> * Add native API docs * Remove generated definitions * Add to gitignore generated openapi files * Updates to docs * Ignore files correction * Remove files created by the plugin * Changes to move the definition files to META-INF * Changes to move the definitions to WEB-INF * Changes to get the files from META-INF * Changed the phase of execution of the smallrye plugin * Changes of names to improve the generation of the spec * Add support for OpenAPI annotations and documents the version endpoint * Multipart Annotations * Typos correction * Changes for tags * Renaming of methods * Changes to the endpoint * Added test * Add test * Deleted extra import * Docs updated * openapi doc tweaks #9981 #10236 * improve release note #9981 #10236 * Remove old test and changes response to JSON * stub out guidance on openapi validation #9981 #10236 * add InfoIT to list of tests * use description of Dataverse from website * mention status codes in openapi doc * update api faq about changelog, link to breaking changes doc * typo * Change to OpenApi * Changes to docs * Name fix * Removing the multipart from unirest --------- Co-authored-by: Philip Durbin <[email protected]>
* Plugin initial config * Initial changes to provide OpenAPI definition * Added integration test * Imports fix * Add patchnotes * Update the changelog * Update src/main/java/edu/harvard/iq/dataverse/api/Info.java Co-authored-by: Philip Durbin <[email protected]> * Update doc/release-notes/10236-openapi-definition-endpoint.md Co-authored-by: Philip Durbin <[email protected]> * Update doc/release-notes/10236-openapi-definition-endpoint.md Co-authored-by: Philip Durbin <[email protected]> * Add native API docs * Remove generated definitions * Add to gitignore generated openapi files * Updates to docs * Ignore files correction * Remove files created by the plugin * Changes to move the definition files to META-INF * Changes to move the definitions to WEB-INF * Changes to get the files from META-INF * Changed the phase of execution of the smallrye plugin * Changes of names to improve the generation of the spec * Add support for OpenAPI annotations and documents the version endpoint * Multipart Annotations * Typos correction * Changes for tags * Renaming of methods * Changes to the endpoint * Added test * Add test * Deleted extra import * Docs updated * openapi doc tweaks IQSS#9981 IQSS#10236 * improve release note IQSS#9981 IQSS#10236 * Remove old test and changes response to JSON * stub out guidance on openapi validation IQSS#9981 IQSS#10236 * add InfoIT to list of tests * use description of Dataverse from website * mention status codes in openapi doc * update api faq about changelog, link to breaking changes doc * typo * Change to OpenApi * Changes to docs * Name fix * Removing the multipart from unirest --------- Co-authored-by: Philip Durbin <[email protected]>
What steps does it take to reproduce the issue?
The
openapi
endpoint provided by Payara results in an internal server error in version 6.0. For example, the endpoint does not function on Demo Dataverse (v6.0), although it does on Harvard's Dataverse (v5.14). Click on each link to reproduce the error.Which version of Dataverse are you using?
Dataverse 6.0
The text was updated successfully, but these errors were encountered: