Hi, thank you for fixing it so quickly.
But I have another issue: Same problem, another bundle: the JMX-management-bundle "org.apache.karaf.admin.management". When loaded lazy, the MBean is not registered and I see no way to activate the bundle manually to get the MBean registered. I know, these functions or not used so often, so if there is a way to activate the bundle "by hand" (in ssh-console or jconsole) it would be sufficient. Do you have any tips? Best regards, Uwe. Guillaume Nodet wrote: > > I think you're right, features-core should be eager by default. or at > least the service itself should be eager. > I'll fix that asap. > > > On Mon, Feb 14, 2011 at 11:35, Uwe K. <[email protected]> wrote: >> >> Hi, >> >> in the trunk and karaf-2.2.x-versions actually the boot-features aren't >> loaded on startup. >> You have to connect to the console and issue at least a "feature:list" >> command to get them installed. >> >> As I see, the default-activation was changed to "lazy" for the >> features/core-bundle (with KARAF-443) . >> >> Am I missing some point, or should this bundle not be loaded in "eager" >> mode, to get it started and the boot-features installed? >> >> Kind regards, >> >> Uwe Korte. >> >> -- >> View this message in context: >> http://karaf.922171.n3.nabble.com/Boot-Features-not-started-tp2491610p2491610.html >> Sent from the Karaf - Dev mailing list archive at Nabble.com. >> > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com > > -- View this message in context: http://karaf.922171.n3.nabble.com/Boot-Features-not-started-tp2491610p2535298.html Sent from the Karaf - Dev mailing list archive at Nabble.com.
