Hi Jean-Baptiste, actually I meant something like the blueprint URL scheme, so that's it. However, the anonymous version (or embedded blueprint within features.xml) is also interesting ;-)
Thanks for the quick help. Kind regards, Jörn Viele Grüße Jörn On Wed, Sep 24, 2014 at 2:33 PM, Jean-Baptiste Onofré <[email protected]> wrote: > Oh by naked, Jörn means: > > <feature name="my" version="1.0"> > <blueprint> > <[CDATA[ > <?xml version="1.0" encoding="UTF-8"?> > <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0";> > .... > </blueprint> > ]]> > </blueprint> > </feature> > > Correct, it's not supported ;) > > Maybe the two workarounds that I sent in my previous e-mail could help. > > Regards > JB > > On 09/24/2014 02:30 PM, Achim Nierbeck wrote: > >> Hi, >> >> no the "naked" one only works for drop-in deployment for a watched >> directory, like the deploy one. The features don't support this, yet. >> >> regards, Achim >> >> >> 2014-09-24 14:25 GMT+02:00 Jörn Gersdorf <[email protected] >> <mailto:[email protected]>>: >> >> Hi karaf-users, >> >> I recently came along the different deployers included in Karaf >> (described at >> http://karaf.apache.org/manual/latest/users-guide/deployers.html), >> in particular the blueprint deployer. >> >> My question: is deployment of a "naked" blueprint xml also supported >> by Karaf´s features.xml? >> >> Thanks. >> >> Kind regards, >> Jörn >> >> >> >> >> -- >> >> 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/> >> >> Software Architect / Project Manager / Scrum Master >> >> > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com >
