cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CXF-3143) SOAPBindingUtil 'leaks' proxy classes
Date Thu, 05 May 2011 01:48:03 GMT

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

Willem Jiang resolved CXF-3143.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.12
                   2.3.1

> SOAPBindingUtil 'leaks' proxy classes
> -------------------------------------
>
>                 Key: CXF-3143
>                 URL: https://issues.apache.org/jira/browse/CXF-3143
>             Project: CXF
>          Issue Type: Bug
>          Components: Soap Binding
>    Affects Versions: 2.3, 2.2.11
>            Reporter: Benson Margulies
>            Assignee: Benson Margulies
>             Fix For: 2.3.1, 2.2.12
>
>
> org.apache.cxf.tools.util.SOAPBindingUtil.getProxy(Class<T>, Object) creates proxies
in the same class loader as the class it is proxying.
> This essentially leaks them,  since the classes being proxied are prone to be in the
system class loader, but the proxies are being created on behalf of the current thread.
> The simplest improvement is to create them in the context class loader, so that (for
example) the wsdl2java mojo can arrange for them to be GC-ed.
> Another interesting question is whether there should be some sort of cache: it seems
to me that we're creating proxies for the same IBM WSDL soap binding impl class over and over.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message