Hi
I've opened an enhancement request:
https://issues.apache.org/jira/browse/CXF-6132
CXF AsyncConduitFactory creates a default manager, but perhaps a custom
instance can be passed to it as a CXF Bus property and set as a factory
field. Later, when a client instance is created, the code dealing with
the default manager instantiation can be skipped if a custom manager is
available.
Can you please check the CXF source and consider providing a minor patch
for Dan to review ? I'm not really familiar with the HC low level API...
Thanks, Sergey
On 26/01/15 14:59, stuart wrote:
Hi
I have HttpClientConnectionManager sub-classed and configured in my
application to make calls to back end ReST services.
We also have SOAP back end services and I need to call them.
We have put a lot of work in to HttpClientConnectionManager configurstion
and require a Pooling connection manager that we can throttle is one place.
I have the WSDL and have used Maven to generate the client
<configuration>
<sourceRoot>${project.build.directory}/generated</sourceRoot>
<wsdlOptions>
<wsdlOption>
<wsdl>${basedir}/src/main/resources/MyWebService-5-0.wsdl</wsdl>
<extraargs>
<extraarg>-client</extraarg>
</extraargs>
<frontEnd>jaxws21</frontEnd>
</wsdlOption>
</wsdlOptions>
</configuration>
We have made the WS call via the generated port and it all works fine,
however:
We need to re-use the HttpClientConnectionManager sub-class so we can manage
all our connections in one place.
Is ther a way to configure CXF to do this.
Regards
Stuart
--
View this message in context:
http://cxf.547215.n5.nabble.com/Using-HttpClientConnectionManager-to-replage-CXF-HttpClien-tp5753547.html
Sent from the cxf-user mailing list archive at Nabble.com.
