-
Notifications
You must be signed in to change notification settings - Fork 495
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
validation error on root dataverse, Internal Server Error after logging in when deploying to Payara 5 #5907
Comments
We definitely INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL to true purposefully, though I don't recall the exact thing that needed it.(possibly the way we handle "required" validation?) Regardless a different solution was found, so am closing the PR that changes this. |
Just tried again at @pdurbin's request, deployed Dataverse 4.17 over Payara 5.193.1. The homepage still shows the validation error displayed above. In my case, even though I specify the FAKE DOI provider the first warning in server.log is a login failure:
Also at @pdurbin's behest I tried #6220 on Payara-5.193.1 after I merged it with develop - same behavior as above. |
Beware... My patch in #6220 does only fix the login issue for the Dataverse ID validation, not for a DOI provider. I did not came across this problem so far. I dunno if I should take a look at this. Depends on @scolapasta... @pdurbin should this be a new issue? Maybe @donsizemore is willing to enable the message dumping, so we get a better error message? |
I'm going to close this, as it is solved in the current version of #6230. |
We're getting a strange error when browsing to the root dataverse when Dataverse is deployed to Payara 5 rather than Glassfish 4.1:
The theory by the non-JSF experts (myself included) over at #4172 (comment) is that it has something to do with this:
Should we try changing it to "false" like this?
The text was updated successfully, but these errors were encountered: