Could http:conduit be configured with Client directly?

[ext2 <xu...@tongtech.com>]

Hi:
	I have check the CXF document, as it said, I could configure a
separate http:conduit with the QName of port. And the client will choice the
conduit matched by the client's port's qname;

	But now I encounter a problem which cannot be resolved by such
http:conduit configuration;

	For example: I am writing a client to invoke two webservice which
wsdl is same;the two webservice both using https, but they ask for different
keystore to authentication;
	That's to say, the two webservice ask for two different http:conduit
while their port qname are same;
	Could CXF enable to configure a http:conduit direct with Client?  If
so , cxf could resolve my problem.

Thanks any suggestion
		

Re: Could http:conduit be configured with Client directly?

[ext2 <xu...@tongtech.com>]

Sorry, regret my foolish;
I found the method which  has be well documented in CXF

> -----Original -----
>Sender: ext2 [mailto:xuhb@tongtech.com]
>Date: 2011年4月28日 11:03
>Receiver: users@cxf.apache.org
> Subject: Could http:conduit be configured with Client directly?
> 
> Hi:
> 	I have check the CXF document, as it said, I could configure a
> separate http:conduit with the QName of port. And the client will choice
the
> conduit matched by the client's port's qname;
> 
> 	But now I encounter a problem which cannot be resolved by such
> http:conduit configuration;
> 
> 	For example: I am writing a client to invoke two webservice which
> wsdl is same;the two webservice both using https, but they ask for
different
> keystore to authentication;
> 	That's to say, the two webservice ask for two different http:conduit
> while their port qname are same;
> 	Could CXF enable to configure a http:conduit direct with Client?  If
> so , cxf could resolve my problem.
> 
> Thanks any suggestion
> 
>