We also go by solution 1. Works pretty well for us. Kind regards, Andreas
On Wed, Oct 22, 2014 at 10:58 PM, Achim Nierbeck <[email protected]> wrote: > Hi, > > I'd go for solution 1. But this is just my 2 cents ;) > > regards, Achim > > 2014-10-21 23:07 GMT+02:00 boodoopl <[email protected]>: > >> Hello, >> >> I wonder how to create custom Karaf 3.0.x distribution with Derby >> datasource >> installed on startup - I mean without need of calling jdbc:create command >> manually. >> >> For now I can see 2 possibilities: >> * Create derby-datasource Blueprint bundle same as on Karaf sources, add >> it >> to feature descriptor which will be set as boot one. >> * Create jdbc-default-selector Blueprint bundle which will use injected >> JdbcService to call create() method during bean init phase, first checking >> by dataSources() if the service has not been already created - it would be >> called on first container starup only >> >> Do you have any other ideas how to say "This custom Karaf distribution is >> shipped with Derby DS" to Karaf nicely? >> >> >> >> -- >> View this message in context: >> http://karaf.922171.n3.nabble.com/Creating-Karaf-custom-distribution-with-JDBC-data-source-tp4036058.html >> Sent from the Karaf - User mailing list archive at Nabble.com. >> > > > > -- > > Apache Member > Apache Karaf <http://karaf.apache.org/> Committer & PMC > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & > Project Lead > blog <http://notizblog.nierbeck.de/> > Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS> > > Software Architect / Project Manager / Scrum Master > >
