Hi Gerry, As per my understanding Conduit is generally used by client/consumer and Destination by server to respond to the request that is to be consumed by consumer.
Are you trying to say you have a Endpoint implementation on Server side which acts like a client for some other service? If this is the case and both Client A and Client B(your old and new client impl.) are using HTTP there shouldn't any need to change the conduit implementation. Can you clarify the scenario bit more ? Regards, Ulhas Bhole On 17 Aug 2011, at 10:41, GerryChenStarNet wrote: > Hi everyone! > > I have a question of CXF Client Transports.Can I replace the HTTPConduit of > Client with other HTTPConduit? > > For example,I have developed a Endpoint in the server. It used to offer the > service for Client A.Now I want to insert another client(I say it Client B) > to the Server And the Client B use the HTTPConduit of Server. > > I think you can say the requestment is strange.But it is real my request. > Because the principle of TR069 protocol ask to do it. > > So someone have some sample on replacing the HTTPConduit of Client with > other HTTPConduit. > I would appreciate it if someone can give me some advice. Thanks a lot. > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/A-question-about-CXF-Client-Transports-tp4707468p4707468.html > Sent from the cxf-user mailing list archive at Nabble.com.
