You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@ace.apache.org by "Bram de Kruijff (JIRA)" <ji...@apache.org> on 2013/05/03 12:24:17 UTC

[jira] [Resolved] (ACE-232) Make Management Agent self contained

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

Bram de Kruijff resolved ACE-232.
---------------------------------

    Resolution: Fixed
      Assignee:     (was: Bram de Kruijff)

As demonstrated by the run-target profile this issue has been covered. The ma runs a a single bundle without requiring any other. Note however we will need to do some more work in the context of ACE-323 /  ACE-324
                
> Make Management Agent self contained
> ------------------------------------
>
>                 Key: ACE-232
>                 URL: https://issues.apache.org/jira/browse/ACE-232
>             Project: ACE
>          Issue Type: Improvement
>          Components: Management Agent
>    Affects Versions: 0.8.0-incubator
>            Reporter: Bram de Kruijff
>         Attachments: ACE-232-selfContainedMA.patch
>
>
> The Management Agent introduced by ACE-91 I (no longer?) self contained as it does not embed its dependencies. As a result, deploying the management agent in an OSGi container requires deploying all its dependencies as well. This will then export all kinds off packages and expose all kinds off services to the environment that may seriously complicate things. 
> The Launcher solves this problem by embedding all the dependencies in the launcher jar providing a controlled way of managing what is (not) exposed into the container.
> My suggestion is to move the embedding to the Management Agent itself providing the same level of control, but now we can deploy the Management Agent into any OSGi container without being forced to use the launcher.
> Eg. This idea triggered cause I want to be able to deploy the Management Agent into a Pax Exam 2 test

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira