[
https://issues.apache.org/jira/browse/ACE-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12910545#action_12910545
]
Marcel Offermans commented on ACE-91:
-------------------------------------
FYI, I committed what I have. It's a stand alone management agent
(ace-managementagent) that embeds all its dependencies. You can deploy it in a
framework, and you can run it as an extension to the framework (as part of the
system bundle). It should even be possible to let it share nothing with the
outside world so it becomes 100% self-contained. So far I briefly tested it and
it "works for me". I do feel that we could strip it a lot more, but that's a
second, separate step.
> 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.
