Hide
I am facing an issue concerning the initialization of easybeans-osgi.
That is:
-We would like to deploy easybeans-osgi bundles onto our clustered application server.
-There are many hosts, with many running osgi frameworks.
-All bundle parameters are stored centrally in a database, and all bundles retrieve their configuration using the standard Osgi "Configuration Admin Service".
-> The problem is: in my understanding (fixme ??) EasyBeans (agent) only loads parameters from a property file somewhere in the filesystem. But we don't/can't distribute the property file on all our hosts.
it would be nice/great if easybeans-agent could load its initial configuration using a "ManagedService", in order to let the EZB agent loads its configuration from our "Configuration Admin" Service ..
Show
I am facing an issue concerning the initialization of easybeans-osgi.
That is:
-We would like to deploy easybeans-osgi bundles onto our clustered application server.
-There are many hosts, with many running osgi frameworks.
-All bundle parameters are stored centrally in a database, and all bundles retrieve their configuration using the standard Osgi "Configuration Admin Service".
-> The problem is: in my understanding (fixme ??) EasyBeans (agent) only loads parameters from a property file somewhere in the filesystem. But we don't/can't distribute the property file on all our hosts.
it would be nice/great if easybeans-agent could load its initial configuration using a "ManagedService", in order to let the EZB agent loads its configuration from our "Configuration Admin" Service ..
Improvement
Closed
Minor
and if we find one, try to read the "configuration.content" property value, and uses it in replacement of the easybeans.xml file
Please close this issue if that solve the problem.
Thanks