Hi Alexander,
Very happy to hear that! This means that we now have some first parts to
reach Java <-> C Interoperability using OSGI bundles!
A first remark I have is the use of the config.properties file. Right
now, the specified server needs to be set as a configuration option
within the config.properties file. This in turn means that we probably
have to automatically generate this file during the start-up of the node
or - even worse - during the startup of the celix service.
I am not really sure what is supported by the launcher at the moment but
wouldn't it be a good idea to have named arguments for the launcher
anyway?
Regards,
Bjoern
On 2014-09-22 17:23, Alexander Broekhuis wrote:
Hi Bjoern,
Thanks for this! I just tried this etcd based discovery together with
the
Amdatu based version, and it works!
The Amdatu version has a few more configuration properties (like the
rootpath), but those are just minor.
If I have some time, I'll try a bit more in the coming week, and either
add
a remark to this issue, or create new ones.
2014-09-19 17:29 GMT+02:00 Bjoern Petri (JIRA) <[email protected]>:
Bjoern Petri created CELIX-152:
----------------------------------
Summary: Added Discovery/ETCD support
Key: CELIX-152
URL: https://issues.apache.org/jira/browse/CELIX-152
Project: Celix
Issue Type: Improvement
Reporter: Bjoern Petri
Assignee: Bjoern Petri
Re-using the discovery_cfg, I added a bundle which supports discovery
based on etcd.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
