If the thread context class loader is null, some sort of lunacy in the JDK 1.6
spikes CXF via JAX-WS
----------------------------------------------------------------------------------------------------
Key: CXF-3002
URL: https://issues.apache.org/jira/browse/CXF-3002
Project: CXF
Issue Type: Bug
Components: Documentation
Affects Versions: 2.2.10
Reporter: Benson Margulies
I'm labelling this a 'documentation' issue since I can't see anything that we
could to in CXF to fix it.
I tried to use CXF via the JAX-WS client API (the Service class) in an
environment where, for reasons unknown to me,
Thread.currentThread().getContextClassLoader() returned null. The resulting use
in the built-in JAX-WS code of Java 1.6 of the default class loader results in
a very strange event: the JDK code successfully loads up the CXF SPI file from
META-INF, but then fails to load the class named therein.
Since, of course, no CXF code has run at this point, I can't see much to do
except to find a place to yell that there has to be a reasonable context class
loader. Either that or complain to (snort) Oracle.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
