Mailing-List: contact users-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@felix.apache.org
Date: Tue, 6 Sep 2016 16:46:38 +0000 (UTC)
From: Alessandro Gherardi <alessandro.gherardi@yahoo.com.INVALID>
Reply-To: Alessandro Gherardi <alessandro.gherardi@yahoo.com>
To: "users@felix.apache.org" <users@felix.apache.org>
Message-ID: <1994305923.456116.1473180398505@mail.yahoo.com>
Subject: Issues with embedded Felix framework and JAXRS
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_456115_1412896026.1473180398500"
References: <1994305923.456116.1473180398505.ref@mail.yahoo.com>
archived-at: Tue, 06 Sep 2016 16:46:46 -0000

------=_Part_456115_1412896026.1473180398500
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,I have a non-OSGi Java app that loads=C2=A0an OSGi bundle=C2=A0by embedd=
ing Felix. The bundle exposes its functionality as an OSGi service. The app=
 accesses the service via a service tracker.=C2=A0The app uses the org.osgi=
.framework.system.packages.extra option so that the service interface and t=
he classes=C2=A0that the interfaces=C2=A0refers to are all loaded by the sa=
me classloader in both the app and the bundle.
The bundle uses Jersey 2.X and the app uses Jersey 1.17. When the app calls=
 the bundle via the service, the Jersey 2.X code throws the following excep=
tion:
Exception in thread "main" java.lang.LinkageError: ClassCastException: atte=
mpting to castfile:/C:/XXX/bin/javax/ws/rs/ext/RuntimeDelegate.class to bun=
dle://59.1:1/javax/ws/rs/ext/RuntimeDelegate.classat javax.ws.rs.ext.Runtim=
eDelegate.findDelegate(RuntimeDelegate.java:146) at javax.ws.rs.ext.Runtime=
Delegate.getInstance(RuntimeDelegate.java:120) at javax.ws.rs.core.UriBuild=
er.newInstance(UriBuilder.java:95)...
Looking at the Jersey source code, it appears that RuntimeDelegate tries to=
 load a concrete subclass via javax.ws.rs.ext.FactoryFinder. FactoryFinder =
reads the name of the subclass from file META-INF/services/javax.ws.rs.ext.=
RuntimeDelegate, and it loads that file via the calling threads's context c=
lass loader. Since the calling thread is an application's thread, its class=
 loader is the application's class loader, so META-INF/services/javax.ws.rs=
.ext.RuntimeDelegate points to a Jersey 1.17 class.
I can kind-of workaround the problem by setting=C2=A0the application thread=
 to an "empty" class loader before calling the service - i.e.:
ClassLoader saveCL =3D Thread.currentThread().getContextClassLoader();
ClassLoader myCL =3D new URLClassLoader(new URL[0], saveCL.getParent());
try {
=C2=A0 Thread.currentThread().setContextClassLoader(myCL);
=C2=A0 call OSGi service
} finally {
=C2=A0 Thrad.currentThread().setContextClassloader(saveCL);
}

However, I'm surprised I have to do that. Shouldn't the framework take care=
 of this - even if the service caller is the embedded application rather th=
an another OSGi bundle?
Notice: This issue may or may not be related to=C2=A0 commons-logging and A=
xis problems
Thank you in advance,Alessandro
 =20
| =20
|  =20
|  =20
|   |    |

   |

  |
| =20
|   | =20
commons-logging and Axis problems
   |   |

  |

  |

=20


------=_Part_456115_1412896026.1473180398500--