Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Message-ID: <21428902.281731284899553531.JavaMail.jira@thor>
Date: Sun, 19 Sep 2010 08:32:33 -0400 (EDT)
From: "Benson Margulies (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Subject: [jira] Updated: (CXF-3002) If the thread context class loader is
 null, some sort of lunacy in the JDK 1.6 spikes CXF via JAX-WS
In-Reply-To: <31999669.281711284899552900.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CXF-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benson Margulies updated CXF-3002:
----------------------------------

    Description: 
I'm labelling this a 'documentation' issue since I can't see anything that we could do 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.

As a footnote, the person who reported this to me did try to get around it by calling CXF APIs explicitly with different weird results that I have not had time to analyze.


  was:
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.


> 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 do 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.
> As a footnote, the person who reported this to me did try to get around it by calling CXF APIs explicitly with different weird results that I have not had time to analyze.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.