Conversation
|
Apparently Payara 7.x has a minor bug - any API call with a colon in it fails. payara/Payara#7777 - looks like we need to wait for 7.2025.3 or 7.2026.1 + |
There's been an unofficial report that this is fixed in 7.2026.1 - can now move forward and try that. |
cmbz
added
FY26 Sprint 15
@qqmyers Hit this when building the warfile, could you please refresh your branch when you get a chance? Thanks! |
|
Tests passed: |
|
|
||
| #### Update Instructions: | ||
|
|
||
| In addition to the standard Payara update instructions and instructions related to Java 21 (do we say more than install Java 21 following standard guidance for your OS?): |
There was a problem hiding this comment.
The above is just a placeholder, obviously. We should take a look at these:
| Copy the following files from the distributed domain.xml version to your domain. I don't know if all of these are required but we don't edit these by default and they have changed over time. | ||
| As with the 6.9 release, at least updating the *.p12 files is important (to get new root certs). | ||
| cacerts.p12 | ||
| default-web.xml |
There was a problem hiding this comment.
| default-web.xml |
| server.policy | ||
| wss-server-config-1.0.xml | ||
| wss-server-config-2.0.xml | ||
|
|
There was a problem hiding this comment.
For default-web.xml, copy it over but put in the changes we need.
| Either update to put Payara in a /usr/local/payara7 dir or perhaps drop to just /usr/local/payara (at QDR /usr/local/payara is a symbolic link so we can change versions easily) | ||
| Any reference to payara6 has to change, e.g. if counter-processor is deployed, the paths in counter-processor-config.yaml and counter_daily.sh have to be updated. | ||
|
|
||
| Copy the following files from the distributed domain.xml version to your domain. I don't know if all of these are required but we don't edit these by default and they have changed over time. |
There was a problem hiding this comment.
Note to self, we'll be copying the old domain1 directory, like we did at #11827 and https://github.com/IQSS/dataverse/releases/tag/v6.9
Co-authored-by: Philip Durbin <philipdurbin@gmail.com>
| <jacc-provider policy-provider="org.glassfish.exousia.modules.def.DefaultPolicy" name="default" policy-configuration-factory-provider="org.glassfish.exousia.modules.def.DefaultPolicyConfigurationFactory"></jacc-provider> | ||
|
|
||
| 2) Add the jvm option: | ||
| <jvm-options>-Djakarta.security.jacc.PolicyFactory.provider=org.glassfish.exousia.modules.def.DefaultPolicyFactory</jvm-options> |
There was a problem hiding this comment.
-Djakarta.security.jacc.policy.provider=org.glassfish.exousia.modules.def.DefaultPolicy should also be added. These are both in the .
| @@ -25,7 +25,7 @@ jobs: | |||
| ref: 'refs/pull/${{ github.event.client_payload.pull_request.number }}/merge' | |||
There was a problem hiding this comment.
FWIW: It appears that the rules for JSF have been tightened with Payara 7. Changes are needed in the xhtml for the assign role and revoke role calls, tweaking what's processed and when the dialog is shown to avoid the validation error and to assure that the assign/revoke calls are made. Whether we have similar errors elsewhere is unknown. These pages are somewhat unique in that they have multiple different panes that trigger changes, whereas most of our code has one save button that updates everything.
There was a problem hiding this comment.
I'm leaving this comment open to remind us that we might need to tweak xhtml pages, adding process="@this" or similar. See aae1cbd.
github-project-automation
bot
moved this from In Review 🔎
to Ready for QA ⏩
in IQSS Dataverse Project
| # JDK 17 builds disabled due to non-essential fails marking CI jobs as completely failed within | ||
| # Github Projects, PR lists etc. This was consensus on Slack #dv-tech. See issue #8094 | ||
| # (This is a limitation of how Github is currently handling these things.) | ||
| # | ||
| #include: | ||
| # - jdk: '17' | ||
| # experimental: true | ||
| # status: "Experimental" |
There was a problem hiding this comment.
@poikilotherm do you think we should make any changes here?
Related (as the comment says):
|
Passed with payara7 2026.2: |
6 participants
What this PR does / why we need it: This PR updates Dataverse to be compatible with Payara
7.2025.27.2026.2 and Java 21. Aside from the doc changes (payara6 -> payara7 etc.) the changes were relatively minor - a couple deprecated annotations we use (NotEmpty, NotBlank) were removed and replaced with new ones, and some of the EE related classes we mock in tests now have a few more methods that have to be overridden.Which issue(s) this PR closes:
Special notes for your reviewer: Someone will need to check the Docker related compose files and documentation to make the relevant updates to Payara and Java. I tried to avoid updating things related to the Keycloak container since it shouldn't need to update to Java 21.
Suggestions on how to test this:
Does this PR introduce a user interface change? If mockups are available, please link/include them here: No
Is there a release notes update needed for this change?: included.
Additional documentation: A good starting point: https://dataverse-guide--12043.org.readthedocs.build/en/12043/installation/prerequisites.html#payara