[
https://issues.apache.org/jira/browse/SLING-12940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18020877#comment-18020877
]
Konrad Windszus edited comment on SLING-12940 at 9/17/25 8:50 AM:
------------------------------------------------------------------
But this fix leads to the user data also no longer available from JR2 for
external events, right? Any way to fix this without removing that functionality
for JR2?
was (Author: kwin):
But this leads to the user data also no longer available from JR2, right? Any
way to fix this without removing that functionality for JR2?
> ResourceChangeListener reads userData from external events
> ----------------------------------------------------------
>
> Key: SLING-12940
> URL: https://issues.apache.org/jira/browse/SLING-12940
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR Resource 3.3.2
> Reporter: Joerg Hoh
> Assignee: Joerg Hoh
> Priority: Major
> Fix For: JCR Resource 3.3.4
>
>
> The JCR ResourceListener reads the userID only when the event is not external
> (only available through the Jackrabbit Event Impl), as currently Oak (as the
> most prominent implementation) does not preserve the user id for external
> events.
> Oak has the same constraint for the userdata (it writes warnings about it),
> but the current implementation of the JCR ResourceListener unconditionally
> tries to read the userdata also from external events.
> We should change this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
