You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by Dieter Wimberger <di...@wimpi.net> on 2008/10/03 19:52:32 UTC
webconsole 1.2.0
Felix:
It seems like the webconsole now has a dependency on SCR.
org.osgi.framework.BundleException: Exception in
org.apache.felix.webconsole.internal.OsgiManagerActivator.start() of
bundle org.apache.felix.webconsole.
Caused by: java.lang.NoClassDefFoundError:
org.apache.felix.scr.ScrService
at
org.apache.felix.webconsole.internal.compendium.ComponentsServlet.class
$(ComponentsServlet.java:60)
at
org
.apache
.felix
.webconsole
.internal.compendium.ComponentsServlet.<clinit>(ComponentsServlet.java:
60)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at org.apache.felix.webconsole.internal.servlet.OsgiManager.class$
(OsgiManager.java:55)
at
org
.apache
.felix
.webconsole.internal.servlet.OsgiManager.<clinit>(OsgiManager.java:105)
at
org
.apache
.felix
.webconsole
.internal.OsgiManagerActivator.start(OsgiManagerActivator.java:35)
Is this per design? I got the impression that usually the Felix
strategy is "Depend on nothing".
Regards,
Dieter
Re: webconsole 1.2.0
Posted by Felix Meschberger <fm...@gmail.com>.
Thanks and Regards
Felix
Dieter Wimberger schrieb:
> Felix:
>
> Good to know. Added FELIX-752 as requested.
>
> Regards,
> Dieter
>
>
> On 3 Oct 2008, at 14:11, Felix Meschberger wrote:
>
>> Hi Dieter,
>>
>> Dieter Wimberger schrieb:
>>> Felix:
>>>
>>> It seems like the webconsole now has a dependency on SCR.
>>>
>>> org.osgi.framework.BundleException: Exception in
>>> org.apache.felix.webconsole.internal.OsgiManagerActivator.start() of
>>> bundle org.apache.felix.webconsole.
>>> Caused by: java.lang.NoClassDefFoundError:
>>> org.apache.felix.scr.ScrService
>>> at
>>> org.apache.felix.webconsole.internal.compendium.ComponentsServlet.class$(ComponentsServlet.java:60)
>>>
>>>
>>> at
>>> org.apache.felix.webconsole.internal.compendium.ComponentsServlet.<clinit>(ComponentsServlet.java:60)
>>>
>>>
>>> at java.lang.Class.forName0(Native Method)
>>> at java.lang.Class.forName(Class.java:169)
>>> at
>>> org.apache.felix.webconsole.internal.servlet.OsgiManager.class$(OsgiManager.java:55)
>>>
>>>
>>> at
>>> org.apache.felix.webconsole.internal.servlet.OsgiManager.<clinit>(OsgiManager.java:105)
>>>
>>>
>>> at
>>> org.apache.felix.webconsole.internal.OsgiManagerActivator.start(OsgiManagerActivator.java:35)
>>>
>>>
>>
>>
>> Yikes ! And I thought I went through this ensuring there was no
>> dependency in this way.
>>
>> Of course this is a bug big time and would warrant a new release.
>> Thinking about this, I consider moving the ComponentsServlet from the
>> web console to the SCR bundle: This would be inline with the Shell
>> Service support of the SCR Bundle, which plugs into the shell service if
>> available. And it removes the dependency from the Web Console.
>>
>>
>>>
>>> Is this per design? I got the impression that usually the Felix strategy
>>> is "Depend on nothing".
>>
>> No way. This is really a bug and not by design.
>>
>> Thanks for bringing this up. Would you mind creating an issue for this,
>> please ? Thanks.
>>
>> Regards
>> Felix
>
Re: webconsole 1.2.0
Posted by Dieter Wimberger <di...@wimpi.net>.
Felix:
Good to know. Added FELIX-752 as requested.
Regards,
Dieter
On 3 Oct 2008, at 14:11, Felix Meschberger wrote:
> Hi Dieter,
>
> Dieter Wimberger schrieb:
>> Felix:
>>
>> It seems like the webconsole now has a dependency on SCR.
>>
>> org.osgi.framework.BundleException: Exception in
>> org.apache.felix.webconsole.internal.OsgiManagerActivator.start() of
>> bundle org.apache.felix.webconsole.
>> Caused by: java.lang.NoClassDefFoundError:
>> org.apache.felix.scr.ScrService
>> at
>> org
>> .apache.felix.webconsole.internal.compendium.ComponentsServlet.class
>> $(ComponentsServlet.java:60)
>>
>> at
>> org
>> .apache
>> .felix
>> .webconsole
>> .internal
>> .compendium.ComponentsServlet.<clinit>(ComponentsServlet.java:60)
>>
>> at java.lang.Class.forName0(Native Method)
>> at java.lang.Class.forName(Class.java:169)
>> at
>> org.apache.felix.webconsole.internal.servlet.OsgiManager.class$
>> (OsgiManager.java:55)
>>
>> at
>> org
>> .apache
>> .felix
>> .webconsole.internal.servlet.OsgiManager.<clinit>(OsgiManager.java:
>> 105)
>>
>> at
>> org
>> .apache
>> .felix
>> .webconsole
>> .internal.OsgiManagerActivator.start(OsgiManagerActivator.java:35)
>>
>
>
> Yikes ! And I thought I went through this ensuring there was no
> dependency in this way.
>
> Of course this is a bug big time and would warrant a new release.
> Thinking about this, I consider moving the ComponentsServlet from the
> web console to the SCR bundle: This would be inline with the Shell
> Service support of the SCR Bundle, which plugs into the shell
> service if
> available. And it removes the dependency from the Web Console.
>
>
>>
>> Is this per design? I got the impression that usually the Felix
>> strategy
>> is "Depend on nothing".
>
> No way. This is really a bug and not by design.
>
> Thanks for bringing this up. Would you mind creating an issue for
> this,
> please ? Thanks.
>
> Regards
> Felix
Re: webconsole 1.2.0
Posted by Felix Meschberger <fm...@gmail.com>.
Hi Dieter,
Dieter Wimberger schrieb:
> Felix:
>
> It seems like the webconsole now has a dependency on SCR.
>
> org.osgi.framework.BundleException: Exception in
> org.apache.felix.webconsole.internal.OsgiManagerActivator.start() of
> bundle org.apache.felix.webconsole.
> Caused by: java.lang.NoClassDefFoundError: org.apache.felix.scr.ScrService
> at
> org.apache.felix.webconsole.internal.compendium.ComponentsServlet.class$(ComponentsServlet.java:60)
>
> at
> org.apache.felix.webconsole.internal.compendium.ComponentsServlet.<clinit>(ComponentsServlet.java:60)
>
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:169)
> at
> org.apache.felix.webconsole.internal.servlet.OsgiManager.class$(OsgiManager.java:55)
>
> at
> org.apache.felix.webconsole.internal.servlet.OsgiManager.<clinit>(OsgiManager.java:105)
>
> at
> org.apache.felix.webconsole.internal.OsgiManagerActivator.start(OsgiManagerActivator.java:35)
>
Yikes ! And I thought I went through this ensuring there was no
dependency in this way.
Of course this is a bug big time and would warrant a new release.
Thinking about this, I consider moving the ComponentsServlet from the
web console to the SCR bundle: This would be inline with the Shell
Service support of the SCR Bundle, which plugs into the shell service if
available. And it removes the dependency from the Web Console.
>
> Is this per design? I got the impression that usually the Felix strategy
> is "Depend on nothing".
No way. This is really a bug and not by design.
Thanks for bringing this up. Would you mind creating an issue for this,
please ? Thanks.
Regards
Felix