Eclipse Community Forums: Equinox » Difference between equinox-osgi 3.3.0 and 3.2.1

Home » Eclipse Projects » Equinox » Difference between equinox-osgi 3.3.0 and 3.2.1

Difference between equinox-osgi 3.3.0 and 3.2.1 [message #112638]

Fri, 27 June 2008 03:41

Eclipse User

Originally posted by: techi_amol.yahoo.com

Hi All,

faced a new issue. I am trying to run grizzly-servlet-webserver-1.8.1.jar
as an osgi bundle. The jar is already osgi compliant and all i did was add
a BundleActivator to it.

I am able to run the bundle successfully with equinox osgi 3.2.1
(org.eclipse.osgi_3.2.1.R32x_v20060919.jar).

However, when I try to run the same bundle on equinox osgi 3.3.0
(org.eclipse.osgi_3.3.0.200704022148.jar) we get a class not found
exception

Caused by: java.lang.NoClassDefFoundError:
javax/management/MBeanRegistration
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.def ineClass(DefaultClassLoader.java:161)
at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineC lass(ClasspathManager.java:501)
at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findCla ssImpl(ClasspathManager.java:471)
at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLoc alClassImpl(ClasspathManager.java:430)
at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLoc alClass(ClasspathManager.java:413)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.fin dLocalClass(DefaultClassLoader.java:189)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findLo calClass(BundleLoader.java:340)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl assInternal(BundleLoader.java:408)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:369)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:357)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loa dClass(DefaultClassLoader.java:83)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319 )
at
mlb.osgi.grizzly.activator.GrizzlyServletLauncherActivator.s tart(GrizzlyServletLauncherActivator.java:19)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$2 .run(BundleContextImpl.java:999)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.s tartActivator(BundleContextImpl.java:993)

Can someone help me understand why this difference?

Re: Difference between equinox-osgi 3.3.0 and 3.2.1 [message #112695 is a reply to message #112638]

Fri, 27 June 2008 09:28

Eclipse User

Originally posted by: ekkehard.gentz-software.de

Amol,
I dont know the differences, but I think that one bundle has an
Package-Import of javax.management ?

you can try to launch with vmargs
-Dorg.osgi.framework.system.packages=javax.management

ekke

Amol Mathur schrieb:
> Hi All,
>
> faced a new issue. I am trying to run
> grizzly-servlet-webserver-1.8.1.jar as an osgi bundle. The jar is
> already osgi compliant and all i did was add a BundleActivator to it.
>
> I am able to run the bundle successfully with equinox osgi 3.2.1
> (org.eclipse.osgi_3.2.1.R32x_v20060919.jar).
>
> However, when I try to run the same bundle on equinox osgi 3.3.0
> (org.eclipse.osgi_3.3.0.200704022148.jar) we get a class not found
> exception
>
> Caused by: java.lang.NoClassDefFoundError:
> javax/management/MBeanRegistration
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.def ineClass(DefaultClassLoader.java:161)
>
> at
> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineC lass(ClasspathManager.java:501)
>
> at
> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findCla ssImpl(ClasspathManager.java:471)
>
> at
> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLoc alClassImpl(ClasspathManager.java:430)
>
> at
> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLoc alClass(ClasspathManager.java:413)
>
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.fin dLocalClass(DefaultClassLoader.java:189)
>
> at
> org.eclipse.osgi.framework.internal.core.BundleLoader.findLo calClass(BundleLoader.java:340)
>
> at
> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl assInternal(BundleLoader.java:408)
>
> at
> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:369)
>
> at
> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:357)
>
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loa dClass(DefaultClassLoader.java:83)
>
> at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319 )
> at
> mlb.osgi.grizzly.activator.GrizzlyServletLauncherActivator.s tart(GrizzlyServletLauncherActivator.java:19)
>
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl$2 .run(BundleContextImpl.java:999)
>
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.s tartActivator(BundleContextImpl.java:993)
>
>
>
> Can someone help me understand why this difference?
>

Previous Topic:	declarative services and eRCP?
Next Topic:	Updating a read-only installation?

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 26 17:39:22 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter