If you are using this to create a DataSource then you might be
interested in:
https://github.com/ops4j/org.ops4j.pax.jdbc/tree/master/pax-jdbc-config
This project create DataSources from config files. Unlike blueprint it
only creates the DataSource once the config is there. So the problem
should not happen.
There is also
https://github.com/ops4j/org.ops4j.pax.jdbc/tree/master/pax-jdbc-pool-aries
and
https://github.com/ops4j/org.ops4j.pax.jdbc/tree/master/pax-jdbc-pool-dbcp2
if you want to add pooling.
Christian
On 13.10.2014 15:48, jkraushaar wrote:
Hi JB,
I've tried your solution, but it does not solve our problem. The
configuration admin service is ready, but does not put the properties into
the data source fast enough. Seems to be a race condition indeed. I think
I'll move to a manual configuration mechanism for the data source instead to
solve the problem.
Thanks
Jochen
--
View this message in context:
http://karaf.922171.n3.nabble.com/Mandatory-Configuration-from-configAdmin-tp4031442p4035861.html
Sent from the Karaf - User mailing list archive at Nabble.com.
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
