felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard S. Hall (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-1980) Gogo TelnetShell cannot be activated
Date Wed, 13 Jan 2010 14:33:55 GMT

    [ https://issues.apache.org/jira/browse/FELIX-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799766#action_12799766
] 

Richard S. Hall commented on FELIX-1980:
----------------------------------------

First, I don't consider the Remote Shell the "old" one. I was talking about telnetD, which
was for Oscar. The property in config.properties for telnet referred to that one.

Second, I was not aware that Remote Shell was using properties on the "osgi.*" namespace,
it should probably rename its properties to be in the "felix." namespace so people don't get
confused and think they are standard properties.

Third, I don't really care about the approach for properties too much neither. Just throwing
out proposals. I am not convinced having separate properties for port, etc. would be confusing,
since they are going to be separate regardless. If you really wanted to go crazy you could
make the property follow OSGi standard syntax and do something like:

   felix.gogo.access=telnet;port:=6666;maxconnect:=5,console

> Gogo TelnetShell cannot be activated
> ------------------------------------
>
>                 Key: FELIX-1980
>                 URL: https://issues.apache.org/jira/browse/FELIX-1980
>             Project: Felix
>          Issue Type: Bug
>          Components: Gogo
>            Reporter: Arjun Panday
>            Priority: Minor
>         Attachments: gogo.tgz
>
>
> Gogo's TelnetShell is implemented as an SCR component but no XML is provided to activate
it. 
> /Arjun

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message