[
https://issues.apache.org/jira/browse/SLING-7761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16532978#comment-16532978
]
Konrad Windszus commented on SLING-7761:
----------------------------------------
I have the same use case in mind. I just still don’t get yet, why this would
force you to use different user data values per package. One global
configuration should be enough. Then all your custom event listeners can be
adjusted to that, right?
> UserData should be set to identify node/property changes in EventListeners
> done through the PackageManager
> ----------------------------------------------------------------------------------------------------------
>
> Key: SLING-7761
> URL: https://issues.apache.org/jira/browse/SLING-7761
> Project: Sling
> Issue Type: Improvement
> Components: Installer
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: Installer Packages Factory 1.0.0
>
>
> There is the method ObservationManager.setUserData(String)
> (https://docs.adobe.com/docs/en/spec/jsr170/javadocs/jcr-2.0/javax/jcr/observation/ObservationManager.html#setUserData(java.lang.String))
> which allows to bind some arbitrary string to the session, so that for each
> event which is being emitted due to {{Session.save()}} from this session this
> user data is available.
> This would allow to determine in an arbitrary
> {{javax.jcr.observation.EventListener}} whether a particular event was caused
> by a package manager installation or not.
> A related change has been implemented in
> https://github.com/Adobe-Consulting-Services/acs-aem-tools/issues/149.
> The actual value should be configurable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
