Hi That's the drawback of using the deploy folder.
However, you can deploy the ds XML using a feature. Regards JB Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: asookazian2 <[email protected]> Date:14/11/2014 23:14 (GMT+01:00) To: [email protected] Cc: Subject: non-deterministic installation order with ds files in deploy dir 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.
