You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (Jira)" <ji...@apache.org> on 2026/02/02 21:11:00 UTC

[jira] [Commented] (JCR-5225) pending removal of java.security.AccessControlException will break JCR API

    [ https://issues.apache.org/jira/browse/JCR-5225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18056051#comment-18056051 ] 

Julian Reschke commented on JCR-5225:
-------------------------------------

FWIW; there's a "dormant" EG (JSR 333).

> pending removal of java.security.AccessControlException will break JCR API
> --------------------------------------------------------------------------
>
>                 Key: JCR-5225
>                 URL: https://issues.apache.org/jira/browse/JCR-5225
>             Project: Jackrabbit Content Repository
>          Issue Type: Task
>          Components: JCR API
>            Reporter: Julian Reschke
>            Priority: Critical
>
> {{java.security.AccessControlException}} is deprecated "for removal" and might disappear in the next LTS release (Java 29, est 2027) (see https://docs.oracle.com/en/java/javase/25/docs/api/java.base/java/security/AccessControlException.html)
> This will break the JCRP API: https://developer.adobe.com/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/javax/jcr/Session.html#checkPermission(java.lang.String,java.lang.String)
> The JCR API de facto is frozen:
> - it's not part of J2EE, so does not have a home at Jakarta (not even considering the impact of the package name change)
> - an actual revision "in place" would require a new JSR and expert group (unlikely, but I'd like to be proven otherwise)
> FWIW, security-dev@openjdk.org is where this can be discussed.
> *_Issue opened here because I couldn't think of a more suitable place to capture this_*



--
This message was sent by Atlassian Jira
(v8.20.10#820010)