Hi Sahoo,

Unfortunately, the attachement has been eaten by the mail forwarder ;-)

You may send it to me in private.

The message regarding the ComponentServlet is caused by the fact, that
you may not be using the Apache Felix SCR implementation, which is
required by the ComponentServlet. This is not a problem and you may
ignore this message.

Regards
Felix

Sahoo schrieb:
> Felix Meschberger wrote:
>> Hi,
>>
>> Sahoo schrieb:
>>  
>>> I was hoping to be able to browse bundles using Felix Web Console, but I
>>> didn't see any way of doing it other than running "ps" shell command
>>> from the web console. Is my observation correct?
>>>     
>>
>> What do you mean by "browse bundles" ? If you go to the bundles page
>> (which is the default page at /system/console/) you get a list of all
>> bundles installed in the system.
>>
>> You can click on the little black arrow to the right of the bundle name
>> of flip open bundle details. Or you may click on the bundle name itself
>> to just display the bundle with its details. This second view can also
>> be directly addressed by going to /system/console/bundles/xyz where xyz
>> is either the bundle ID or the bundle symbolic name.
>>   
> This is exactly the functionality I was looking for, but it does not
> seem to work for me. I am using webconsole version #1.2.2 on top my own
> HTTP Service Implementation which uses web container from GlassFish v3.
> GlassFish v3 itself runs on top of Felix 1.2.2. I am attaching the
> screenshot of what I see. May be you can tell me what's going wrong
> here. FYI, I see some warning in our server log:
> /
> Failed to instantiate plugin
> org.apache.felix.webconsole.internal.compendium.ComponentsServlet.
> Reason: java.lang.NoClassDefFoundError: org.apache.felix.scr.ScrService
> /
> Can this be the cause?
> 
> I should also inform you that there may be bugs in my implementation of
> HTTP service implementation, but I would like to know what they are. I
> have been able to run a couple of test cases using the same service and
> they seem to have worked.
> 
> Thanks,
> Sahoo
> 
> 
> ------------------------------------------------------------------------
> 
> ---------------------------------------------------------------------
> 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