[
https://issues.apache.org/jira/browse/SLING-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-1590.
-----------------------------------
> OSGi events should contain a userID when possible.
> --------------------------------------------------
>
> Key: SLING-1590
> URL: https://issues.apache.org/jira/browse/SLING-1590
> Project: Sling
> Issue Type: Improvement
> Components: API, JCR
> Affects Versions: JCR Resource 2.0.8, API 2.0.8
> Reporter: Simon Gaeremynck
> Assignee: Justin Edelson
> Fix For: JCR Resource 2.0.8, API 2.1.0
>
> Attachments: userids-in-events.diff
>
>
> We're building a system that tracks the user's movements in the system.
> One of the things we're tracking is the OSGi events that are emitted by
> Sling. These don't contain a userid however.
> Since this all hapens in the JcrResourceListener which is a JCR Observation
> Listener, getting the userID is fairly straightforward.
> I'll attach a patch that includes this functionality.
> AFAICT this is the only location that emits user generated events, if I
> missed a spot I'd be happy to try and patch that one as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
