Thanks JB, solution 2 fits perfectly. For other users having the same problem: I created a wrapper bundle containing the blueprint data source definition as suggested. The blueprint file also holds configuration parameters as described here: http://www.liquid-reality.de/display/liquid/2011/09/23/Karaf+Tutorial+Part+2+-+Using+the+Configuration+Admin+Service The configuration parameters are used to define URL, user name and password of the data source. I also created a configuration file stored in folder etc. So the credentials of the data source can easily be changed. Then I added the wrapper bundle to my feature and set the start level accordingly.
Regards Jochen -- View this message in context: http://karaf.922171.n3.nabble.com/How-to-deploy-data-source-before-EJB-JPA-bundle-tp4033529p4033569.html Sent from the Karaf - User mailing list archive at Nabble.com.
