ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Angelo van der Sijpt (JIRA)" <>
Subject [jira] [Commented] (ACE-101) Allow the discovery service to be pluggable
Date Sun, 22 Apr 2012 14:41:34 GMT


Angelo van der Sijpt commented on ACE-101:

I like the solution with adding the bundle to the class path, and providing the activator;
however, I'm not so sure about the system property to disable the property-based discovery

I think this solution actually consists of two parts: one is the 'fat bundle' (known as the
management agent bundle), which should somehow pick up external services for discovery and
identification. The other is this launcher, which should give you a mechanism for starting
bundles alongside the management agent. What about using something like

 java -cp org.apache.ace.launcher-0.8.1-SNAPSHOT.jar:my.own.discovery-0.0.1.jar activators=my.own.discovery.Activator

in which I provide my own bundle for discovery, and configure the 'default' mechanism for
identification. The default discovery service is not configured in this way, and will fall
back to it's default value; however, my.own.discovery bundle provides a Discovery service
with a higher service rank, so it gets picked up.
> Allow the discovery service to be pluggable
> -------------------------------------------
>                 Key: ACE-101
>                 URL:
>             Project: ACE
>          Issue Type: Sub-task
>            Reporter: Angelo van der Sijpt
> The launcher has to be as self-contained as possible; yet, we want to be able to drop
in a Discovery service, which will then take precedence over the system property.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message