ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Offermans (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACE-430) Deployment events should propagate from the agent to EventAdmin, if available
Date Thu, 17 Apr 2014 08:53:23 GMT

     [ https://issues.apache.org/jira/browse/ACE-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Marcel Offermans updated ACE-430:
---------------------------------

    Fix Version/s: next

> Deployment events should propagate from the agent to EventAdmin, if available
> -----------------------------------------------------------------------------
>
>                 Key: ACE-430
>                 URL: https://issues.apache.org/jira/browse/ACE-430
>             Project: ACE
>          Issue Type: Improvement
>            Reporter: Marcel Offermans
>            Assignee: Marcel Offermans
>             Fix For: next
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message