You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ace.apache.org by "Toni Menzel (JIRA)" <ji...@apache.org> on 2010/09/17 11:43:54 UTC
[jira] Assigned: (ACE-91) Create fat bundle ace gateway
[ https://issues.apache.org/jira/browse/ACE-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Toni Menzel reassigned ACE-91:
------------------------------
Assignee: Toni Menzel
> Create fat bundle ace gateway
> -----------------------------
>
> 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.
-
You can reply to this email to add a comment to the issue online.