-
Notifications
You must be signed in to change notification settings - Fork 306
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
Payara Micro 5.2020.5: OpenAPI document creation failed / FISH-760 #4955
Comments
In my case this works in 5.2020.4 but not in 5.2020.5. |
Hi, Can you link to a reproducer that shows this behavior so that we can investigate this further. Best Regards |
Hi @Herr-Sepp, can you provide a simple to follow scenario how to reproduce this on the latest release of Payara Community Edition? A reproducer should ideally follow the SSCCE rules: http://www.sscce.org/. It will greatly help us to find the cause and fix it. |
I get the very same exception since upgrading from 5.2020.4 to 5.2020.6. Will try to provide a reproducer in the next couple of days. |
It does not seem to be very easy to reproduce. I tried to build a simple example with only one REST resource two response and two response objects and the OpenAPI document is created. Our full application with > 15 resources and many request and response objects fails on 2020.5 & 2020.6 Maybe @ThomasPr has more luck. |
Hi @ThomasPr, have you had any luck with a reproducer? I'm keeping this issue open longer than usual incase you have came up with a reproducer - otherwise we will have to close this issue soon due to lack of reproducer. |
I have the same problem. |
I think I found a way to reproduce it. In my case it's an enum in an
Works in 2020.4 but not in 2020.6 I'm going to create a repo for this reproducer. |
I created a quick demo to show the issue I found that the issue would be occurred when there is an endpoint require a request body and the request body contains an Enum field |
@VeitWeber also spotted on the Enum, so it may be really the root cause :) |
Just for the records, because the use case is slightly different than @hei1233212000 's one. https://github.com/VeitWeber/pay4955 I don't even use the Enum in the request. |
Hi All, Thank you for the quick responses, I have been able to reproduce this issue with both @VeitWeber and @hei1233212000's reproducer with the latest version. I have created an internal issue Thank you, |
Hi, I closed this issue as it is solved by the OpenAPI 2.0 upgrade which included a patch to correctly handle Enums. To be clear, this issue was caused by the presence of the Enum (regardless of whether it's used by endpoints). You may also be interested in #5130, as OpenAPI applications without Best regards, Matt |
Description
I was hoping that in 5.2020.5 the OpenAPI bugs are fixed(#4832) , unfortunately I still get the null pointer exception on first call of /openapi.
Maybe it's the old problem again that the micro-docker container doesn't contain the right version?
Because:
Expected Outcome
Response 200 with OpenAPI-Document
Current Outcome
404 Not Found
If i request /openapi again then i get the document back, but many endpoints are missing.
Environment
The text was updated successfully, but these errors were encountered: