The first stage is to make sure your blueprint file is processed at all.
So make sure it is at the correct location (OSGI-INF/blueprint/*.xml)
and that the namespace is correct.
If the file is processed you should see logging messages and the bundle
list should show the blueprint status too.
In karaf 3 you can try the diag command which also shows blueprint errors.
If you see nothing then try to increase the log verbosity using log:set
debug.
Christian
Am 18.06.2014 17:56, schrieb Leschke, Scott:
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
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
