Walid "jo" Gedeon wrote:
Thanks Alin. I'm going to try the pax shell in a couple of hours -- after
work :-)
Do you have a copy of the RFC to share? I'd be interested in casting a look
at its contents... ;-)
It is not possible to give out the RFC since it is an internal document,
but the early release R4.2 spec might contain a snapshot.
-> richard
w
On Thu, Oct 23, 2008 at 2:46 PM, Alin Dreghiciu <[EMAIL PROTECTED]>wrote:
There is already a very basic telnet implementation but for sure we
can benefit from your expertise in the domain.
With the new spec and Pax Shell implementation it is quite easy to add
a new connector. We already provide at least basic connectors for
stdin, telnet, web and jabber.
On Thu, Oct 23, 2008 at 2:58 PM, Walid jo Gedeon <[EMAIL PROTECTED]>
wrote:
Thanks for the info Stuart.
yes, it would be good to have this spec'd - and I believe this is
actually
in progress.
I'll be waiting impatiently for the RFC, hopefully on time to get review
and
feedback.
FYI, there's some OSGi shell code that Alin has been working on over at
OPS4J:
http://lists.ops4j.org/pipermail/general/2008q3/008111.html
it's based on Peter Kriens prototype
Cool, I'll check it out.
I had started getting some research done to integrate my telnetservice
functionality (http://telnetservice.sourceforge.net/); the two efforts
may
actually complete one another... I havent uploaded the osgi compliant
version of the modules yet, but if it's of interest I can :-)
w
On Thu, Oct 23, 2008 at 11:45 AM, Stuart McCulloch <[EMAIL PROTECTED]
wrote:
2008/10/23 Walid jo Gedeon <[EMAIL PROTECTED]>
It does, thanks richard.
I'm not a big fan of passing PrintStreams for command execution output
and
error, but the command that can be looked up like a service is cool. I
had
hopes there was a "standard" interface definition ;-)
One goal of adopting osgi would be the possibility to write a
component
and
be able to deploy it on any compliant implementation, I'm wondering
why
such
an interface is not in the spec...
yes, it would be good to have this spec'd - and I believe this is
actually
in progress
FYI, there's some OSGi shell code that Alin has been working on over at
OPS4J:
http://lists.ops4j.org/pipermail/general/2008q3/008111.html
it's based on Peter Kriens prototype, the latest code can be downloaded
from:
https://scm.ops4j.org/repos/ops4j/projects/pax/shell/
send a note to [EMAIL PROTECTED] for more information about the
status
and how it relates to the ongoing command shell spec...
I'll check in that direction some more; for now all i found was this
article
on the top news section [
http://blog.ciscavate.org/2008/10/auto-documenting-osgi-commandproviders.html
].
w
On Wed, Oct 22, 2008 at 6:22 PM, Richard S. Hall <
[EMAIL PROTECTED]
wrote:
The documentation is incorrect. The "ungoverned" package was from
when
Felix was Oscar. The "apache" packages are correct. I have edited
the
document to fix this issue. Let me know if it makes more sense now.
-> richard
Walid "jo" Gedeon wrote:
Hello all,
Browsing through the available docs to understand how commands work
in
felix
(specifically, but in osgi in general), the shell service page
seemed
to
make sense (
http://felix.apache.org/site/apache-felix-shell-service.html)<
http://felix.apache.org/site/apache-felix-shell-service.html%29>
.<http://felix.apache.org/site/apache-felix-shell-service.html%29.>
..
... until the section "Creating a Command" :-)
I'm not sure I get why MyStartCommandImpl implements
org.apache.felix.shell.Command and not
org.ungoverned.osgi.service.shell.Command? Or alternatively why
doesnt
org.apache.felix.shell.Command extend it...
Thanks for any comments or points of vue:-)
w
--
Cheers, Stuart
--
Alin Dreghiciu
http://www.ops4j.org - New Energy for OSS Communities - Open
Participation Software.
http://www.qi4j.org - New Energy for Java - Domain Driven
Development.
http://malaysia.jayway.net - New Energy for Projects - Great People
working on Great Projects at Great Places
