Thanks for the tips. I stripped everything down to the basic example in the
manual, and it seems the problem I was having is some kind of blueprint
issue. When I run the example console extension, my bundle starts in the
GracePeriod and the log diplays:
13:13:04,435 | WARN | rint Extender: 3 |
The namespace you use is wrong, it should be
http://karaf.apache.org/xmlns/shell/v1.0.0
On Sun, Jan 23, 2011 at 19:18, Adam Crain acr...@greenenergycorp.com wrote:
Thanks for the tips. I stripped everything down to the basic example in the
manual, and it seems the problem I was having is
Hmm. I guess I accidently took that from the felix tutorially. Thanks, the
example is working now!
Where can I find some examples of using blueprint to do DI for osgi
services? My shell extension requires some services to already be registered
so that it can invoke them in doExecute.
best,
Adam
Searching through Karaf source, I noticed that OsgiCommandSupport has a
getBundleContext method. I can just use that to see if the services I need
are there when the command is invoked. Is this considered bad practice?
On Sun, Jan 23, 2011 at 2:21 PM, Adam Crain acr...@greenenergycorp.comwrote:
How do I implement a console extension without blueprint?
I created a BundleActivator and tried to publish the service
OsgiCommandSupport guessing that would cause the system to pickup the new
shell command, but I was wrong.
thanks,
Adam
