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] [Closed] (ACE-395) Multi deployment package support at least by a predictable order
Date Tue, 05 Nov 2013 13:37:35 GMT

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

Marcel Offermans closed ACE-395.
--------------------------------

    Resolution: Won't Fix

This can now be done by implementing your own "controller" for the new management agent.

> Multi deployment package support at least by a predictable order
> ----------------------------------------------------------------
>
>                 Key: ACE-395
>                 URL: https://issues.apache.org/jira/browse/ACE-395
>             Project: ACE
>          Issue Type: Improvement
>          Components: Deployment
>            Reporter: Andrej Zachar
>            Priority: Blocker
>
> Dear Apache Ace committers!
> We would like to deploy multiple deployment packages managed by org.apache.ace.management
that have cross references!
> The problem is that one deployment packages have some cross  references to other bundle
in the other deployment packages. If they are deployed in a wrong other, the whole application
is working.
> Image situation:
> Application deployment package
>  +bundle 1 (requires licence bundle that is available in the other deloyment package)
>  +bundle n (requires licence bundle)
> Licence deployment package
>  +licence bundle
> To solve this issue I have introduced a simple solution: an order that tells org.apache.ace.management
which agent has priority over the other agent.
> This approach allows me to keep deployment packages isolated, but I can tell which deployment
package (more precious which agent) will deploy first. 
> For that reason I have also introduced many small improvements and before I will describe
them all I want to know If there is an interest to cooperate on this topic.
> Here is some overview of changes:
> 1. Deployment of fragments and large packages (introduced Time Outs param)
> 2. Improved logging
>     
> 3. Simplified the configuration folder structure for  local agent's repositories
> Thank you very much for your answer.
> Best regards,
> Andrej



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message