Allright I've figured it out... The problem was with the H2 JDBC driver that I was using.
For folks encountering this issue: Recent H2 releases come with a new manifest and implement the org.osgi.service.jdbc.DataSourceFactory service. To satisfy this H2 dependency I've written a feature that include the H2 driver and the org.osgi.compendium bundle. The latter basically breaks the Blueprint deployer resulting in "Bundle is not compatible with this blueprint extender" warnings. Perhaps I've should have used PAX JDBC in this case, but I haven't tried. Downgrading to H2 version 1.3.167 fixes the issue. On Tue, Feb 4, 2014 at 5:48 PM, cbiava <[email protected]> wrote: > Hi Richard, > > I tried on 2.3.3 and 3.0.0 and it It worked fine. Does your xml file looks > like that ? : > > <?xml version="1.0" encoding="UTF-8"?> > <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0";> > > <bean id="BasedataSourceName" > class="oracle.jdbc.pool.OracleDataSource"> > <property name="URL" > value="jdbc:oracle:thin:@adresse:port:DB_NAME" /> > <property name="user" value="username" /> > <property name="password" value="userpassword" /> > </bean> > > <service interface="javax.sql.DataSource" ref="BasedataSourceName"> > <service-properties> > <entry key="osgi.jndi.service.name" > value="jdbc/DB_NAME"/> > </service-properties> > </service> > </blueprint> > > Christophe. > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Blueprint-deployer-doesn-t-expose-OSGi-service-properties-tp4031493p4031522.html > Sent from the Karaf - User mailing list archive at Nabble.com. >
