[
https://issues.apache.org/jira/browse/FELIX-4446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922547#comment-13922547
]
Guillaume Nodet commented on FELIX-4446:
----------------------------------------
Could you please look at the patch ? It's not very big and quite easy to read
imho, so your questions would be answered ;-)
For the record, I didn't want to hack with the Event class which is provided by
the osgi alliance or hack using reflection, so I've rather chosen to create a
new event, but only when that's needed. The problem with hacking the api is
that the it can be imported, so this would mean that the implementation has no
real control.
For the user, I understand this might be a bit specific to my use, but I'm
using the currently authenticated jaas user.
Those two behaviors are disabled by default using configuration properties, and
lead to no overhead by default (the copy is only done if a property will be
added).
> 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)
