A quick way, I have found is to use org.slf4j.Logger and log an info statement in your init method. You see pretty quick when you start your bundle that things are working.
If you don't see the message, then: * Where is your activator.xml located? (Under OSGI-INF/blueprint) * What is the format of you blueprint file? Is it valid? (I find that using the XML Validator in Netbeans or Eclipse works good before deploy as well.) On Wed, Jun 18, 2014 at 10:56 AM, Leschke, Scott <[email protected]> wrote: > I’m trying to get familiar with Blueprint. I don’t think a Blueprint > container is being created for my bundle because I don’t see a message in > the log saying it’s been destroyed when I shut Karaf down. I assume that’s > a pretty good indicator. > > > > If that’s correct, is there a good way to diagnose Blueprint issues? > > > > Scott > -- Scott Carr
