I looked at Christian's tutorial here: http://www.liquid-reality.de/display/liquid/2011/09/23/Karaf+Tutorial+Part+2+-+Using+the+Configuration+Admin+Service
However, I don't see anything that specifically says that the Blueprint container will not start until the configuration is provided. Also, does this mean that the configuration file is there or that each property I try to reference is there? On Wed, Jun 13, 2012 at 11:00 AM, Achim Nierbeck <[email protected]> wrote: > Hi James, > > you need to use managed Services via the Configuration Admin service. > Take a look at the blueprint documentation to find some more details > on how to create that. > Or take a look at some of those tutorials christian did. (I'm sure he > has a link in his signature :) ) > > regards, Achim > > 2012/6/13 James Carman <[email protected]>: >> On Tue, Jun 12, 2012 at 4:59 PM, Christian Schneider >> <[email protected]> wrote: >>> >>> >>> You probably use start levels to work around this. OSGi services and >>> blueprint should help you >>> with this. You can make sure bundles only start when required services or >>> configs are present. >>> >> >> We actually don't mess with start levels. Blueprint will put the >> bundle into the "Grace Period" until it finds everything it needs. >> However, I am intrigued by that last part there where you said I can >> tell BP to only start when required configs are present. How do I >> stall the BP startup when configs aren't present? > > > > -- > > Apache Karaf <http://karaf.apache.org/> Committer & PMC > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> > Committer & Project Lead > OPS4J Pax for Vaadin > <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project > Lead > blog <http://notizblog.nierbeck.de/>
