cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CXF-3002) If the thread context class loader is null, some sort of lunacy in the JDK 1.6 spikes CXF via JAX-WS
Date Mon, 27 Mar 2017 17:51:41 GMT

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

Daniel Kulp resolved CXF-3002.
------------------------------
       Resolution: Won't Fix
         Assignee: Daniel Kulp
    Fix Version/s: Invalid


This issue is ancient and I haven't seen anything like it since it was logged so no idea if
there is anything we need/can do about it or even have to do about it.   

> 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
>            Assignee: Daniel Kulp
>             Fix For: Invalid
>
>
> 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 was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message