You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by Craig Phillips <lc...@praxiseng.com> on 2008/07/25 13:32:44 UTC
How to use web console
Hi, Good morning,
Sorry to trouble y'all for probably something I otherwise could have
figured out on my own, but no such luck...
I have the web console bundle loaded, resolved, and started (I grabbed
the javax.servlet bundle from my eclipse3.4 plugins directory)...
I'm not sure how to point my browser to it (web console, that is)...
I did a netstat -a, but don't see any obvious listening ports...
Obviously, I'm missing something to the riddle...
Thanks, Craig
PS - I followed the OSGi spec and implemented a publisher/subscriber
model straight off the spec on the first try using felix eventAdmin! I
do appreciate how folks pay allegiance to the spec and point out where
there's divergence or shortcomings - very nice;
RE: How to use web console
Posted by Craig Phillips <lc...@praxiseng.com>.
Ahh, much better! Thanks! Very nice... Craig
-----Original Message-----
From: Pedro Pedruzzi [mailto:ppedruzzi@v2com.mobi]
Sent: Friday, July 25, 2008 8:43 AM
To: dev@felix.apache.org
Subject: Re: How to use web console
Try:
http://localhost:8080/system/console/
On Fri, Jul 25, 2008 at 9:36 AM, Craig Phillips
<lc...@praxiseng.com> wrote:
> Hi,
>
> Using the eclipse34 plugins, I managed to get
> http/jetty/web-console/port-8080 going... unfortunately, when I
connect
> to localhost:8080, this is what I get???
>
> ----------------------------
> HTTP ERROR: 404
> ProxyServlet: /
> RequestURI=/
> Powered by Jetty://
> -----------------------------
>
> Any ideas? Thanks again, Craig
>
> -----Original Message-----
> From: Felix Meschberger [mailto:fmeschbe@gmail.com]
> Sent: Friday, July 25, 2008 8:23 AM
> To: dev@felix.apache.org
> Subject: Re: How to use web console
>
> Hi,
>
> I come to the same conclusion as Pedro. You might for example want to
> install the Apache Felix http.jetty bundle or the OPS4J Pax Web
Service
> bundle.
>
> Both should be configured to listen to port 8888 by default (IIRC).
>
> This should do the trick. Hope this helps.
>
> Regards
> Felix
>
> Pedro Pedruzzi schrieb:
>> Hi!
>>
>> On Fri, Jul 25, 2008 at 8:32 AM, Craig Phillips
>> <lc...@praxiseng.com> wrote:
>>> Hi, Good morning,
>>>
>>> Sorry to trouble y'all for probably something I otherwise could have
>>> figured out on my own, but no such luck...
>>>
>>> I have the web console bundle loaded, resolved, and started (I
> grabbed
>>> the javax.servlet bundle from my eclipse3.4 plugins directory)...
>>>
>>> I'm not sure how to point my browser to it (web console, that is)...
>>>
>>> I did a netstat -a, but don't see any obvious listening ports...
>>>
>>> Obviously, I'm missing something to the riddle...
>>>
>>> Thanks, Craig
>>>
>>> PS - I followed the OSGi spec and implemented a publisher/subscriber
>>> model straight off the spec on the first try using felix eventAdmin!
> I
>>> do appreciate how folks pay allegiance to the spec and point out
> where
>>> there's divergence or shortcomings - very nice;
>>
>> My guess is that there is no bundle providing a HTTP Service.
>>
>> You could check that with the 'sevices' command, in the felix shell
>> and look for:
>> org.osgi.service.http.HttpService
>>
>> Regards,
>>
>> --
>> Pedro Pedruzzi
>>
>
--
Pedro Pedruzzi | Engenharia de Software | V2COM | +55 11 3094-3939
Re: How to use web console
Posted by Pedro Pedruzzi <pp...@v2com.mobi>.
Try:
http://localhost:8080/system/console/
On Fri, Jul 25, 2008 at 9:36 AM, Craig Phillips
<lc...@praxiseng.com> wrote:
> Hi,
>
> Using the eclipse34 plugins, I managed to get
> http/jetty/web-console/port-8080 going... unfortunately, when I connect
> to localhost:8080, this is what I get???
>
> ----------------------------
> HTTP ERROR: 404
> ProxyServlet: /
> RequestURI=/
> Powered by Jetty://
> -----------------------------
>
> Any ideas? Thanks again, Craig
>
> -----Original Message-----
> From: Felix Meschberger [mailto:fmeschbe@gmail.com]
> Sent: Friday, July 25, 2008 8:23 AM
> To: dev@felix.apache.org
> Subject: Re: How to use web console
>
> Hi,
>
> I come to the same conclusion as Pedro. You might for example want to
> install the Apache Felix http.jetty bundle or the OPS4J Pax Web Service
> bundle.
>
> Both should be configured to listen to port 8888 by default (IIRC).
>
> This should do the trick. Hope this helps.
>
> Regards
> Felix
>
> Pedro Pedruzzi schrieb:
>> Hi!
>>
>> On Fri, Jul 25, 2008 at 8:32 AM, Craig Phillips
>> <lc...@praxiseng.com> wrote:
>>> Hi, Good morning,
>>>
>>> Sorry to trouble y'all for probably something I otherwise could have
>>> figured out on my own, but no such luck...
>>>
>>> I have the web console bundle loaded, resolved, and started (I
> grabbed
>>> the javax.servlet bundle from my eclipse3.4 plugins directory)...
>>>
>>> I'm not sure how to point my browser to it (web console, that is)...
>>>
>>> I did a netstat -a, but don't see any obvious listening ports...
>>>
>>> Obviously, I'm missing something to the riddle...
>>>
>>> Thanks, Craig
>>>
>>> PS - I followed the OSGi spec and implemented a publisher/subscriber
>>> model straight off the spec on the first try using felix eventAdmin!
> I
>>> do appreciate how folks pay allegiance to the spec and point out
> where
>>> there's divergence or shortcomings - very nice;
>>
>> My guess is that there is no bundle providing a HTTP Service.
>>
>> You could check that with the 'sevices' command, in the felix shell
>> and look for:
>> org.osgi.service.http.HttpService
>>
>> Regards,
>>
>> --
>> Pedro Pedruzzi
>>
>
--
Pedro Pedruzzi | Engenharia de Software | V2COM | +55 11 3094-3939
RE: How to use web console
Posted by Craig Phillips <lc...@praxiseng.com>.
Hi,
Using the eclipse34 plugins, I managed to get
http/jetty/web-console/port-8080 going... unfortunately, when I connect
to localhost:8080, this is what I get???
----------------------------
HTTP ERROR: 404
ProxyServlet: /
RequestURI=/
Powered by Jetty://
-----------------------------
Any ideas? Thanks again, Craig
-----Original Message-----
From: Felix Meschberger [mailto:fmeschbe@gmail.com]
Sent: Friday, July 25, 2008 8:23 AM
To: dev@felix.apache.org
Subject: Re: How to use web console
Hi,
I come to the same conclusion as Pedro. You might for example want to
install the Apache Felix http.jetty bundle or the OPS4J Pax Web Service
bundle.
Both should be configured to listen to port 8888 by default (IIRC).
This should do the trick. Hope this helps.
Regards
Felix
Pedro Pedruzzi schrieb:
> Hi!
>
> On Fri, Jul 25, 2008 at 8:32 AM, Craig Phillips
> <lc...@praxiseng.com> wrote:
>> Hi, Good morning,
>>
>> Sorry to trouble y'all for probably something I otherwise could have
>> figured out on my own, but no such luck...
>>
>> I have the web console bundle loaded, resolved, and started (I
grabbed
>> the javax.servlet bundle from my eclipse3.4 plugins directory)...
>>
>> I'm not sure how to point my browser to it (web console, that is)...
>>
>> I did a netstat -a, but don't see any obvious listening ports...
>>
>> Obviously, I'm missing something to the riddle...
>>
>> Thanks, Craig
>>
>> PS - I followed the OSGi spec and implemented a publisher/subscriber
>> model straight off the spec on the first try using felix eventAdmin!
I
>> do appreciate how folks pay allegiance to the spec and point out
where
>> there's divergence or shortcomings - very nice;
>
> My guess is that there is no bundle providing a HTTP Service.
>
> You could check that with the 'sevices' command, in the felix shell
> and look for:
> org.osgi.service.http.HttpService
>
> Regards,
>
> --
> Pedro Pedruzzi
>
Re: How to use web console
Posted by Felix Meschberger <fm...@gmail.com>.
Hi,
I come to the same conclusion as Pedro. You might for example want to
install the Apache Felix http.jetty bundle or the OPS4J Pax Web Service
bundle.
Both should be configured to listen to port 8888 by default (IIRC).
This should do the trick. Hope this helps.
Regards
Felix
Pedro Pedruzzi schrieb:
> Hi!
>
> On Fri, Jul 25, 2008 at 8:32 AM, Craig Phillips
> <lc...@praxiseng.com> wrote:
>> Hi, Good morning,
>>
>> Sorry to trouble y'all for probably something I otherwise could have
>> figured out on my own, but no such luck...
>>
>> I have the web console bundle loaded, resolved, and started (I grabbed
>> the javax.servlet bundle from my eclipse3.4 plugins directory)...
>>
>> I'm not sure how to point my browser to it (web console, that is)...
>>
>> I did a netstat -a, but don't see any obvious listening ports...
>>
>> Obviously, I'm missing something to the riddle...
>>
>> Thanks, Craig
>>
>> PS - I followed the OSGi spec and implemented a publisher/subscriber
>> model straight off the spec on the first try using felix eventAdmin! I
>> do appreciate how folks pay allegiance to the spec and point out where
>> there's divergence or shortcomings - very nice;
>
> My guess is that there is no bundle providing a HTTP Service.
>
> You could check that with the 'sevices' command, in the felix shell
> and look for:
> org.osgi.service.http.HttpService
>
> Regards,
>
> --
> Pedro Pedruzzi
>
Re: How to use web console
Posted by Pedro Pedruzzi <pp...@v2com.mobi>.
Hi!
On Fri, Jul 25, 2008 at 8:32 AM, Craig Phillips
<lc...@praxiseng.com> wrote:
> Hi, Good morning,
>
> Sorry to trouble y'all for probably something I otherwise could have
> figured out on my own, but no such luck...
>
> I have the web console bundle loaded, resolved, and started (I grabbed
> the javax.servlet bundle from my eclipse3.4 plugins directory)...
>
> I'm not sure how to point my browser to it (web console, that is)...
>
> I did a netstat -a, but don't see any obvious listening ports...
>
> Obviously, I'm missing something to the riddle...
>
> Thanks, Craig
>
> PS - I followed the OSGi spec and implemented a publisher/subscriber
> model straight off the spec on the first try using felix eventAdmin! I
> do appreciate how folks pay allegiance to the spec and point out where
> there's divergence or shortcomings - very nice;
My guess is that there is no bundle providing a HTTP Service.
You could check that with the 'sevices' command, in the felix shell
and look for:
org.osgi.service.http.HttpService
Regards,
--
Pedro Pedruzzi