Review: CCR for Azul/Payara Community (Web Profile) 7.2026.5 — Jakarta EE 11 Web Profile

[Copilot]

Reviews the compatibility certification request for Azul/Payara Community (Web Profile) 7.2026.5 against Jakarta EE 11 Web Profile, following the CCR Review Guidance. This is a review-only task; the repository stores no certification records, so no source files were changed. Findings are captured in this PR description and a repository memory of the EE 11 Web Profile required-TCK set was stored for future reviews.

Verification cross-references the two accepted EE 11 Web Profile CCRs (#1290 Open Liberty, #1291 WebSphere Liberty), which share an identical set of 17 required standalone TCKs.

Passed

• Both final attestation checkboxes (EFTL + all TCK requirements met) checked
• Main Platform TCK on official download.eclipse.org/jakartaee/ base URL (jakarta-jakartaeetck-11.0.1.zip)
• TCK Results Summary hosted on a product-associated, permanent page (docs.payara.fish)

Blocking — missing required standalone TCKs

• Jakarta Data 1.0 — absent (required; present in Compatibility certification request for Open Liberty for Jakarta EE 11, Web Profile #1290/Compatibility certification request for IBM WebSphere Liberty for Jakarta EE 11, Web Profile #1291)
• Jakarta Debugging Support for Other Languages 2.0 — absent (required)

To confirm with filer

• Authentication 3.1.0 SHA-256 9421c6ca…d5ac4d is actually the published hash of the Annotations 3.0.0 TCK — likely copy/paste error
• Dependent TCK versions trail the accepted set: Authentication 3.1.0→3.1.1, Faces 4.1.1→4.1.2, RESTful WS 4.0.0→4.0.1, Servlet 6.1.0→6.1.1, EL 6.0.0→6.0.1 — confirm against Platform TCK 11.0.1 requirements
• Specification listed as "Jakarta EE Platform 11.0"; should be Jakarta EE Web Profile 11
• Jakarta Tags 3.0.1 listed but not part of the required standalone set (harmless)
• Results Summary link is malformed in the issue (stray %20/broken markdown)

Recommendation

Not ready for approval. Add the missing Jakarta Data and Jakarta Debugging Support standalone TCKs and correct the Authentication SHA-256 before recommending.

Note: download.eclipse.org and docs.payara.fish are unreachable from the review sandbox, so link-liveness and byte-level SHA recomputation were not performed directly; SHA/version findings derive from comparison with the two accepted EE 11 Web Profile CCRs.

[ivargrimstad]

See PR text and issue comment

[Copilot]

See PR text and issue comment

Re-reviewed and verified each hash live against the official <tck>.zip.sha256 sidecars on download.eclipse.org (rather than comparing to prior CCRs). Updated findings in the PR description. Summary:

4 SHA-256 mismatches: Authentication 3.1.0 (listed value is actually the Annotations hash), Annotations 3.0.0, Concurrency 3.1.1, CDI 4.1.0.

2 broken URLs (404): Annotations jakarta-annotation-tck → should be jakarta-annotations-tck (plural); CDI /ee4j/cdi/4.0/ → should be /jakartaee/cdi/4.1/.

2 missing required standalone TCKs: Jakarta Data 1.0 and Jakarta Debugging Support 2.0.

Plus minor items (spec should read "Jakarta EE Web Profile 11"; TCK labeled "11.0" vs actual 11.0.1; malformed Results Summary link). Recommendation: not ready for approval. Note: payara.fish hosts are unreachable from the sandbox, so the product download and Results Summary "all tests pass" could not be verified directly.