It's because the feature resolver (based on the felix resolver) is used.
You should add breakpoint in the felix resolver.
Regards
JB
On 08/24/2015 01:36 PM, Benson Margulies wrote:
Yes, plus I edited bin/karaf to add suspend=y in case it had to do
with something at startup. I get as far as FeatureServiceImpl
debugging 'down' before I got a bit lost and tried to come up from the
other direction. Whenever I do 'feature:install feature' (yea, a dumb
name) I see all this activity related to standard pieces of Karaf that
should already be installed, and I never see any mention of the
feature I'm actually trying to install, but I presumably don't have
the right breakpoint yet. I wonder if the root of this is that I've
configured the thing as a bootFeature in an assembly.
(I'm surprised that you don't seem to keep a framework listener after
startup; I discovered that (in equinox, at least, which I'm _not_
using here) wiring error details are only reported as framework
events.)
On Mon, Aug 24, 2015 at 7:30 AM, Jean-Baptiste Onofré <[email protected]> wrote:
Did you use KARAF_DEBUG and a remote debugger ?
Regards
JB
On 08/24/2015 01:18 PM, Benson Margulies wrote:
I'd be happy to work on debugging my own issue here; but I could use a
hint. I breakpointed all the calls to installBundle that I could
find, and none of them were hit. So I'm apparently barking up the
wrong tree. Anyone care to point me at a neighborhood that would
decide not to load a bundle because has an un-wirable import?
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
