You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ace.apache.org by "Marcel Offermans (Resolved) (JIRA)" <ji...@apache.org> on 2011/10/28 17:57:32 UTC
[jira] [Resolved] (ACE-91) Create self contained management agent
[ https://issues.apache.org/jira/browse/ACE-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Offermans resolved ACE-91.
---------------------------------
Resolution: Fixed
Has been implemented in the ace-managementagent module.
> Create self contained management agent
> --------------------------------------
>
> Key: ACE-91
> URL: https://issues.apache.org/jira/browse/ACE-91
> Project: Ace
> Issue Type: New Feature
> Reporter: Toni Menzel
> Assignee: Toni Menzel
>
> Ace has a very losly coupled bundle partitioning (many small bundles). Which is a good thing.
> But to be able to drop in ace gateway functionality (lets say, taking over an existing, already running osgi fw instance), or to minimize potential implications on other bundles ( for example when having "bad" bundles flying around which could mess up the stability of the gateway), it might be worth to offer a fat bundle distribution of a default, fully configured, ace gateway.
> This includes:
> - single bundle. just export ace api. imports on minimal java api + osgi core / cmpd only.
> - default/auto configuration
> - audits enabled (?)
> As a proof of functionality, one could drop the bundle on an eclipse ide, which should make it possible to immediately see it on a remote ace server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira