[ACE-430] Deployment events should propagate from the agent to EventAdmin, if available

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0.1
• Assignee: Marcel Offermans
• Reporter: Marcel Offermans
• Created: 15/Nov/13 09:04
• Updated: 17/Apr/14 08:56
• Resolved: 17/Apr/14 08:56

Description

Our new management agent contains an internal implementation of EventAdmin that is used in the DeploymentAdmin bundle to capture the events it throws, regardless of the availability of a "real" EventAdmin implementation.

That is good.

What it fails to do however, is propagate those events to a "real" EventAdmin if that is available. That is bad because resource processors or other code might want to listen to those events (or even depend on them, because the specification requires them to be sent).

We should therefore propagate events to an EventAdmin service, if we find one, without creating a dependency on EventAdmin, which would break the isolation we have now between the agent and the rest of the framework.