removal of AccessControlException vs javax.jcr
Alan Bateman
alan.bateman at oracle.com
Sat Jan 24 08:44:52 UTC 2026
On 23/01/2026 19:00, Julian Reschke wrote:
> Am 23.01.2026 um 19:00 schrieb Sean Mullan:
>> It hasn't been removed yet, but the plan is to eventually remove it.
>> Why is it frozen? Depending on a library or project that isn't active
>> or cannot be adapted seems a bit concerning.
>> ...
>
> It's a Javax API. The only way to change/revise/update it would be a
> new JSR xxx Expert Group, unless I'm missing something.
I don't know anything about this Content Repository API but I agree with
Sean that it is a bit concerning to be dependent on something that might
no longer be maintained. I see the last update to the API was 2009 but I
can't tell if this is one of these APIs with multiple implementations
maintained by different projects. Do you know if anyone has been
maintaining an implementation has tested it on JDK 7 or newer? As the
API was developed in the JCP then it may be that it needs a maintenance
JSR to update. This assumes of course that it is still relevant and
intended to work with modern JDK releases.
-Alan
More information about the security-dev
mailing list