Using the deploy folder often creates such problems. I generally advise
people to only use the deploy
folder for first experiements and proof of concepts.
For production I recommend to put the blueprint.xml files into a bundle
and deploy them this way.
For the special purpose of creating a DataSource there is a new option
pax-jdbc-config:
https://ops4j1.jira.com/wiki/display/PAXJDBC/Create+DataSource+from+config
It allows to create the DataSource from a pure config. The release is
expected during the next days.
Christian
Am 14.11.2014 23:14, schrieb asookazian2:
I've been testing a feature install which requires a foo-ds.xml (datasource)
to be copied into the karaf/deploy dir first and then the 'feature:install
bar' executed next. It seems that the order of installation of the foo-ds
bundle may be before or after the feature bundle installs. If the foo-ds
bundle is activated after the depending bundle is activated, then I see an
exception in the log (something like a JNDI lookup error and the datasource
can't be found). If I restart karaf, all bundles end up in Active state due
to the start-level configs (the foo-ds.xml bundle start-level is 80 and the
depending bundle is 85).
What is the best way to handle this so all bundles are guaranteed to be
Active state after feature install? We've discussed adding a <sleep
seconds="5"/> after the foo-ds.xml copy to deploy dir and prior to the
feature install. Is there any better way to handle this? Another idea was
to have a loop in the ant install script which checks the foo-ds.xml
bundle's state and once it is Active then install the feature. thx.
--
View this message in context:
http://karaf.922171.n3.nabble.com/non-deterministic-installation-order-with-ds-files-in-deploy-dir-tp4036433.html
Sent from the Karaf - User mailing list archive at Nabble.com.
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
