Cluing in with your blog post as a starting point, I've also found this handy reference[1] over at Felix.
Perhaps a wiki link from the Karaf page[2] to the RFC-147 Overview[1] would be helpful. Cheers, Andreas [1] http://felix.apache.org/site/rfc-147-overview.html [2] http://felix.apache.org/site/61-extending-the-console.html On Jan 6, 2010, at 9:35 AM, David Savage wrote: > Hi Andreas, > > Glad about the first comment, apologies about the second :) > > Regards, > > Dave > > On Wed, Jan 6, 2010 at 2:12 PM, Andreas Kollegger > <[email protected]> wrote: >> Hi Dave, >> >> Your blog post was perfect: informative and the cause for me wasting >> a half hour watching the Star Wars ASCIImation this morning. >> >> Cheers, >> Andreas >> >> On Jan 6, 2010, at 6:17 AM, David Savage wrote: >> >>> Hi Andreas, >>> >>> Karaf now uses gogo for the cli support which is based on RFC 147 from >>> the OSGi alliance - I've blogged about writing cli commands for RFC >>> 147 here [1] - actually the example uses Nimble [2] vs Karaf but the >>> same rules apply as they're both RFC 147 shell environments. >>> >>> Hope that helps. >>> >>> Regards, >>> >>> Dave >>> >>> [1] http://bit.ly/8MDjCl >>> [2] http://bit.ly/8fnBhK >>> >>> On Tue, Jan 5, 2010 at 10:14 PM, Andreas Kollegger >>> <[email protected]> wrote: >>>> Hi all, >>>> >>>> I'd like to add some shell commands to interact with my registered >>>> services. Much like adding >>>> a web UI, I intend to put the commands in a separate, optional bundle. >>>> >>>> The Karaf guide has a nice page[1] on adding console commands. It uses >>>> Blueprint to register the >>>> command, which is fine except that it isn't clear to me how to use >>>> Blueprint to inject references to >>>> the services for which I'm providing a text UI. Is there a reference >>>> somewhere for that? >>>> >>>> Alternatively, I'd use Peaberry to inject the dependencies and register >>>> the command. Looking at the >>>> example command during runtime I only see a BlueprintContainer service for >>>> the bundle. >>>> >>>> Is there non-blueprint way to register a command? >>>> >>>> Thanks, >>>> Andreas >>>> >>>> [1] http://felix.apache.org/site/61-extending-the-console.html >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
