Hi Derek,

Thanks for your quick response.
I'd still prefer using Telnet for now and indeed it seems to work fine..
I've just created JIRA FELIX-1980 and attached a simple modification to the Activator and TelnetShell.

/Arjun


Le 01/12/2010 04:56 PM, Derek Baum a écrit :
Hi Arjun,

The original contribution of Gogo (from Peter Kriens) contained SCR
components, but we replaced them with regular Activators, as Gogo is usually
started very early, before SCR support is available:
http://felix.apache.org/site/apache-felix-gogo.html

The GoGo TelnetShell is a very simple implementation, but I prefer to use
ssh (which is bundled with Karaf, which also uses GoGo). However, the
TelnetShell does work, so we should provide a regular Activator for this.

Derek

2010/1/12 Arjun Panday<[email protected]>

Hi,

I've started playing with Gogo (and it seems great!) but I need to use it
via telnet.
I noticed that the console module had 2 "activators":
- one regular BundleActivator that only creates the StdioConsole
- one SCR component that creates the TelnetShell
but I find no XML (or Service-Component header) for the SCR component, so
the TelnetShell just sits there but is never activated.

If I simply repackage with my own XML as below, it works great:
<?xml version="1.0" encoding="utf-8"?>
<component name="GogoTelnet">
<implementation class="org.apache.felix.gogo.console.telnet.TelnetShell"/>
<reference name="commandProc"
interface="org.osgi.service.command.CommandProcessor"
    bind="setProcessor"/>
</component>

My question is:
- why is there no SCR XML provided? is it on purpose or just forgotten?
- and why mixing Activator and SCR? Everything (Stdio and Telnet) could be
set either by the BundleActivator or SCR components and the property
"osgi.shell.telnet=on" in Felix properties could be used to enable the
telnet part..

thanks,
Arjun


---------------------------------------------------------------------
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]

Reply via email to