JamesHillyard

Hi @jansupol, With thanks to @pzygielo who submitted a contribution to fix this, this issue has been resolved in Payara 6.2022.1.Alpha4 and will be fixed in the upcoming Payara 5.2022.4...

Hi @FlorianFehring, Thank you for your patience, this issue has actually been raised before and is currently in development with the ID `FISH-6298`, I believe the fix implemented by this...

Hi @FlorianFehring, As your original reproducers aren't available, I am unable to confirm if the recent fix `FISH-6298` resolves your issue, however as of Payara Community 5.2022.3 the generated OpenAPI...

Hi @berniegsfc, @StevenHachel, @Yuliamz I have been able to reproduce a slightly different but similar error on Payara Community 5.2022.3, could you please confirm if this is the error you...

Hi @berniegsfc, Thanks for confirming this is still present on Payara 5.2022.3, and you are right this error doesn't seem to have any adverse effects and can be safely ignored....

Hi @berniegsfc, Thank you for your response, it was very useful! That confirms that we are getting the same exception, my stacktrace just doesn't include: ``` Cannot invoke "String.equals(Object)" because...

> I think the error message is different on Java 8. This is absolutely correct, I get the exact same error when using JDK 17 but the error I originally...

Hi all, This issue has been resolved in the latest version of Payara Community, 5.2022.3. Please upgrade your environments to resolve this issue. Thanks, James

Hi @LarsBrenker @YotillaAntoni, This was a breaking change caused by the integration of security connectors, as you identified. As a result our documentation was modified to state Microprofile Config Properties...

Hi @skiedrowski, As a PR has recently been raised to implement this enhancement, it is being tracked under the internal ID `FISH-6578`. Thanks, James