[
https://issues.apache.org/jira/browse/FELIX-4446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923654#comment-13923654
]
Carsten Ziegeler commented on FELIX-4446:
-----------------------------------------
What about doing a general approach and provide a way to filter events? For
example maybe by adding a filter service interface and all events are first run
through this filter. You can then provide an implemetation adding those
properties in your application code.
We could think about getting this into a new version of the event admin spec if
deemed useful
> Optionally enhance event admin to add a timestamp and the authenticated
> subject before dispatching events
> ---------------------------------------------------------------------------------------------------------
>
> Key: FELIX-4446
> URL: https://issues.apache.org/jira/browse/FELIX-4446
> Project: Felix
> Issue Type: New Feature
> Components: Event Admin
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
>
> EventAdmin is great because various bundles do send events, so it's really
> nice for an audit trail of what happened.
> However, in order for the audit trail to be useful, it's missing a few
> properties such as the timestamp and the user performing the action.
> It would be nice if event admin add those automatically to avoid modifying
> various projects to add those properties.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
