Thanks! I did not actually see much in the console, but the logfile on the other said there was a problem finding a property fetcher, which I was missing for my bean. I also corrected the name of the setter, and it now works fine in a 2.1.2 karaf!
Now I have other problems, pax-runner is not able to provision this into a bare felix or equinox in a way that makes blueprint work. But thats another story I guess. On Thu, Nov 25, 2010 at 23:56, Guillaume Nodet <[email protected]> wrote: > I don't see anything wrong in your files. > You give give a try to the following: > * download karaf 2.1.2 just released > * launch it > * in the console. run: "log:set debug" > * copy your blueprint file in the deploy folder > * in the console, run "log:display" > and give me back the output. > > 2010/11/25 John Bäckstrand <[email protected]>: > > 2010/11/25 John Bäckstrand <[email protected]> > > > >> 2010/11/25 John Bäckstrand <[email protected]> > >> > >>> On Wed, Nov 24, 2010 at 22:50, Alasdair Nottingham <[email protected] > >wrote: > >>> > >>>> > It seems the blueprint bundle is not doing anything proactively when > I > >>>> just > >>> > >>> > deploy my bundle together with the blueprint one. > >>>> > >>>> Where do you get your blueprint implementation from? > >>>> > >>>> I tried this with a gemini (eclipse?) implementation and now I am > using > >>> an aries snapshot that I compiled from SVN. > >>> > >>> I see that ares using sl4j for logging, but how do I set the loglevel? > I > >>> am using pax runner and I set the log level for that to debug, but it > does > >>> not seem to affect anything else. > >>> > >>> I will try to produce a smaller sample that I can post, but at the > moment > >>> the code is a bit messy. > >>> > >> > >> > >> I managed to finally set the loglevel. This is all I see from blueprint: > >> > >> 2010-nov-25 21:55:26 > org.apache.aries.blueprint.container.BlueprintExtender > >> start > >> VARNING: Starting blueprint extender... > >> 2010-nov-25 21:55:26 > >> org.apache.aries.blueprint.container.BlueprintEventDispatcher <init> > >> FIN: EventAdmin package is not available, just don't use it > >> 2010-nov-25 21:55:26 > org.apache.aries.blueprint.container.BlueprintExtender > >> start > >> INFO: No quiesce support is available, so blueprint components will not > >> participate in quiesce operations > >> 2010-nov-25 21:55:26 > org.apache.aries.blueprint.container.BlueprintExtender > >> start > >> FIN: Blueprint extender started > >> > >> I changed one of them to warn just to see it, but other than that it > should > >> be straight from SVN. When I stop or start my own bundle nothing is > printed. > >> > >> What is supposed to take place, and using what mechanism? > >> > > > > Oops, to quick on the send button. I created a gist on github with the > most > > important files: > > > > https://gist.github.com/715909 > > > > Sorry for the noisy pom... > > > > > > -- > > John Bäckstrand > > > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- John Bäckstrand
