camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CAMEL-4430) Using the ClientFactoryBean instead of ProxyFactoryBean to create the Client for the CxfProducer
Date Sat, 10 Sep 2011 05:59:08 GMT

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

Willem Jiang resolved CAMEL-4430.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 2.8.2

Applied patch into trunk and Camel 2.8.x branch.

> Using the ClientFactoryBean instead of ProxyFactoryBean to create the Client for the
CxfProducer
> ------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-4430
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4430
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-cxf
>            Reporter: Willem Jiang
>            Assignee: Willem Jiang
>             Fix For: 2.8.2, 2.9.0
>
>
> As the proxy lifecycle cleanup work are done in CXF 2.4.3, we are facing some test failed
in camel-cxf.
> After digging the code, I found the proxy instance which is created by the CxfProxyFactoryBean
will be GC and the CXF client which is used in CxfProducer will be affect. The endpoint which
is set on the conduit will gone, and CxfProducer will complain it with a NPE exception. We
can use the CxfClientFactoryBean to create client instead of CxfProxyFactoryBean to avoid
the GC and NPE exception.
> I checked the difference between using CxfProxyFactoryBean and CxfClientFactoryBean,
they are same in most case.
> We just need to take care of handler setting part which is used in JAXWS frontend.
>  

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

        

Mime
View raw message