You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Walid \"jo\" Gedeon" <wg...@gmail.com> on 2008/10/22 18:02:28 UTC
org.apache.felix.shell.Command
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)...
... 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
Re: org.apache.felix.shell.Command
Posted by "Walid \"jo\" Gedeon" <wg...@gmail.com>.
That's okay :-) I guess I'll just wait for the 4.2 spec to come out!
I don't have access to osgi stuff either (yet?) I'm not sure if I can apply
as a 'freelance' Supporter, I guess I'll just try and fax it in and see
what's the response :-)
Ta!
On Thu, Oct 23, 2008 at 3:56 PM, Richard S. Hall <he...@ungoverned.org>wrote:
> ...
> 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
>
Re: org.apache.felix.shell.Command
Posted by "Richard S. Hall" <he...@ungoverned.org>.
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 <ad...@gmail.com>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 <wg...@gmail.com>
>> 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 <mcculls@gmail.com
>>> wrote:
>>>
>>>
>>>> 2008/10/23 Walid jo Gedeon <wg...@gmail.com>
>>>>
>>>>
>>>>> 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 general@lists.ops4j.org 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 <
>>>>>
>> heavy@ungoverned.org
>>
>>>>>> 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
>>
>>
>
>
Re: org.apache.felix.shell.Command
Posted by Alin Dreghiciu <ad...@gmail.com>.
Unfortunately I do not have it anymore. I had read it some times ago,
when as part of OSGo Alliance I was able to do that. But nowdays this
is not possible anymore.
Maybe Peter K., can send it to you if he will read this thread.
On Thu, Oct 23, 2008 at 4:34 PM, Walid jo Gedeon <wg...@gmail.com> 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... ;-)
> w
>
> On Thu, Oct 23, 2008 at 2:46 PM, Alin Dreghiciu <ad...@gmail.com>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 <wg...@gmail.com>
>> 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 <mcculls@gmail.com
>> >wrote:
>> >
>> >> 2008/10/23 Walid jo Gedeon <wg...@gmail.com>
>> >>
>> >> > 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 general@lists.ops4j.org 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 <
>> heavy@ungoverned.org
>> >> > >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
>>
>
--
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
Re: org.apache.felix.shell.Command
Posted by Guillaume Sauthier <Gu...@objectweb.org>.
There is also an ongoing effort in OW2 JOnAS to provide a framework
independent, extensible and dynamic shell:
http://svn.forge.objectweb.org/cgi-bin/viewcvs.cgi/jonas/sandbox/shelbie/trunk/shelbie/
It have been tested under Felix, Equinox with linux, windows, macosx and
it's using iPOJO under the cover.
Regards
--Guillaume
Walid "jo" Gedeon a écrit :
> Thanks Guillaume. Integrating with Felix's existing shell service is not
> complicated, my initial goal was to implement a framework independent telnet
> console ;-)
>
> On Thu, Oct 23, 2008 at 3:52 PM, Guillaume Nodet <gn...@gmail.com> wrote:
>
>
>> You could also have a look at ServiceMix Kernel which provides an
>> enhanced shell on top of Felix and much more.
>> http://servicemix.apache.org/kernel/index.html
>>
>> --
>> Cheers,
>> Guillaume Nodet
>> ------------------------
>> Blog: http://gnodet.blogspot.com/
>> ------------------------
>> Open Source SOA
>> http://fusesource.com
>>
>>
>
>
Re: org.apache.felix.shell.Command
Posted by "Walid \"jo\" Gedeon" <wg...@gmail.com>.
Thanks Guillaume. Integrating with Felix's existing shell service is not
complicated, my initial goal was to implement a framework independent telnet
console ;-)
On Thu, Oct 23, 2008 at 3:52 PM, Guillaume Nodet <gn...@gmail.com> wrote:
> You could also have a look at ServiceMix Kernel which provides an
> enhanced shell on top of Felix and much more.
> http://servicemix.apache.org/kernel/index.html
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
Re: org.apache.felix.shell.Command
Posted by Guillaume Nodet <gn...@gmail.com>.
You could also have a look at ServiceMix Kernel which provides an
enhanced shell on top of Felix and much more.
http://servicemix.apache.org/kernel/index.html
On Thu, Oct 23, 2008 at 3:34 PM, Walid jo Gedeon <wg...@gmail.com> 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... ;-)
> w
>
> On Thu, Oct 23, 2008 at 2:46 PM, Alin Dreghiciu <ad...@gmail.com>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 <wg...@gmail.com>
>> 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 <mcculls@gmail.com
>> >wrote:
>> >
>> >> 2008/10/23 Walid jo Gedeon <wg...@gmail.com>
>> >>
>> >> > 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 general@lists.ops4j.org 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 <
>> heavy@ungoverned.org
>> >> > >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
>>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Re: org.apache.felix.shell.Command
Posted by "Walid \"jo\" Gedeon" <wg...@gmail.com>.
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... ;-)
w
On Thu, Oct 23, 2008 at 2:46 PM, Alin Dreghiciu <ad...@gmail.com>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 <wg...@gmail.com>
> 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 <mcculls@gmail.com
> >wrote:
> >
> >> 2008/10/23 Walid jo Gedeon <wg...@gmail.com>
> >>
> >> > 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 general@lists.ops4j.org 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 <
> heavy@ungoverned.org
> >> > >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
>
Re: org.apache.felix.shell.Command
Posted by Alin Dreghiciu <ad...@gmail.com>.
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 <wg...@gmail.com> 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 <mc...@gmail.com>wrote:
>
>> 2008/10/23 Walid jo Gedeon <wg...@gmail.com>
>>
>> > 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 general@lists.ops4j.org 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 <heavy@ungoverned.org
>> > >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
Re: org.apache.felix.shell.Command
Posted by "Walid \"jo\" Gedeon" <wg...@gmail.com>.
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 <mc...@gmail.com>wrote:
> 2008/10/23 Walid jo Gedeon <wg...@gmail.com>
>
> > 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 general@lists.ops4j.org 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 <heavy@ungoverned.org
> > >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
>
Re: org.apache.felix.shell.Command
Posted by Stuart McCulloch <mc...@gmail.com>.
2008/10/23 Walid jo Gedeon <wg...@gmail.com>
> 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 general@lists.ops4j.org 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 <heavy@ungoverned.org
> >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.>
> ..
> >> ... 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
Re: org.apache.felix.shell.Command
Posted by "Walid \"jo\" Gedeon" <wg...@gmail.com>.
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...
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 <he...@ungoverned.org>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)...
>> ... 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
>>
>>
>>
>
Re: org.apache.felix.shell.Command
Posted by "Richard S. Hall" <he...@ungoverned.org>.
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)...
> ... 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
>
>