prevent JSF validation error on Payara 5 #4172 #5933
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The issue for supporting Payara 5 at #4172 and the issue for not being locked to Glassfish 4.1 at #2628 are both related but this is a "small chunk" fix that I don't believe causes any problems on Glassfish 4.1. Thank you to @smillidge for the suggestion at #4172 (comment)
Here is the error that I am trying to prevent on Payara 5.192 when visiting the home page of Dataverse:
I see #4172 as representing full support for Payara 5 in the sense of an updated Dataverse Installation Guide, etc. so this pull request is not intended as a fix for that issue. Rather, the idea is to do no harm to existing Dataverse installations on Glassfish 4.1 but help move the needle on Payara 5 support.