You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2023/10/05 13:20:00 UTC

[jira] [Commented] (SLING-12076) ResourceListener should expose the JCR observation's user data

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

Carsten Ziegeler commented on SLING-12076:
------------------------------------------

I think thats done deliberately as resource providers can create these and those are defined in the spi package

> ResourceListener should expose the JCR observation's user data
> --------------------------------------------------------------
>
>                 Key: SLING-12076
>                 URL: https://issues.apache.org/jira/browse/SLING-12076
>             Project: Sling
>          Issue Type: Improvement
>            Reporter: Konrad Windszus
>            Priority: Major
>
> The ResourceChange (https://github.com/apache/sling-org-apache-sling-api/blob/f58111baf07b6ae525aec2c6792e949786df7beb/src/main/java/org/apache/sling/api/resource/observation/ResourceChange.java#L50) should optionally expose a context (arbitrary String). In the case of the JCR Resource Provider this should be populated by the JCR Event's User Data (https://developer.adobe.com/experience-manager/reference-materials/spec/jcr/2.0/12_Observation.html#12.3.5%20User%20Data).



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