ace-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Offermans (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (ACE-171) Refactor the log listener to distinguish between different deployment packages
Date Tue, 06 Sep 2011 12:06:10 GMT

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

Marcel Offermans closed ACE-171.
--------------------------------

    Resolution: Won't Fix

After some thought, I decided not to do this, but in stead rely on the server being able to
distinguish between different deployment packages, "recognizing the right one" and properly
handling all others. This needs to be done anyway, since you could confuse the management
agent by installing a deployment package manually and we did not cater for that at all.

> Refactor the log listener to distinguish between different deployment packages
> ------------------------------------------------------------------------------
>
>                 Key: ACE-171
>                 URL: https://issues.apache.org/jira/browse/ACE-171
>             Project: Ace
>          Issue Type: Sub-task
>            Reporter: Marcel Offermans
>            Assignee: Marcel Offermans
>
> The log listener currently sends life cycle events to a single audit log. We need it
to send these events to all audit logs, and distinguish between events generated by a deployment
package that belongs to its management agent instance and those generated by other deployment
packages. We probably want to introduce new events for the latter category.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message