Payara 6: Embargo selection fails from Dataverse page, works from file page.

[kcondon]

Found while testing Payara 6 branch: #9685
Selecting embargo from the dataset page, either from the individual file kebab or the edit files menu, results in a popup that says selected files are already published and cannot be embargoed, along with a stack trace. The popup and stack trace appear to be the same in both cases.

embargo_fail_datasetpg_editfiles.txt
embargo_fail_datasetpg_file_kebab.txt

Selecting embargo from the files page, edit files button, works but shows the same stack trace in the logs
embargo_success_filepg_editfile.txt

So, it seems like the failure is initializing the popup due to null, but for some reason the error handling from the file page allows it to proceed anyway but from the dataset page it seems to go to an incorrect, perhaps default error?

[scolapasta]

One thing I noticed is that if you then click the embargo a 2nd time, it does show a differently "incorrect" popup. but this also happens if you click on a file that is already published - that is it shows the some part of the popup that would be correct for the "previous" file.