You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2009/12/10 04:07:18 UTC

[jira] Resolved: (CXF-1203) Dynamic client screws up the thread context classloader

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

Daniel Kulp resolved CXF-1203.
------------------------------

       Resolution: Fixed
    Fix Version/s: Invalid
         Assignee: Daniel Kulp


This is mostly a Documentation issue.  I've updated the docs for the DynamicClient stuff to point this out.

> Dynamic client screws up the thread context classloader
> -------------------------------------------------------
>
>                 Key: CXF-1203
>                 URL: https://issues.apache.org/jira/browse/CXF-1203
>             Project: CXF
>          Issue Type: Bug
>          Components: JAXB Databinding
>    Affects Versions: 2.0.2
>            Reporter: Daniel Kulp
>            Assignee: Daniel Kulp
>             Fix For: Invalid
>
>
> The dynamic client sets the ContextClassloader for the thread to a new value at client create time, but doesn't restore it.    Thus, if you then use something else later, the class loader doesn't contain the expected classes.
> The most specific issue is that if you create TWO dynamic clients in the same VM on the same thread, the second one will fail to compile as the classpath is not setup properly.

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