Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <4DF8B9CB.9020808@die-schneider.net>
Date: Wed, 15 Jun 2011 15:55:23 +0200
From: Christian Schneider <chris@die-schneider.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de;
 rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: dev@camel.apache.org
Subject: Re: [Discussion] Remove cxf: component
References: <4DF8B444.7090608@die-schneider.net> <4DF8B7E3.4070208@gmail.com>
In-Reply-To: <4DF8B7E3.4070208@gmail.com>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit

Hi Willem,

could you give a small example for creating a proxy using the cxf component?

Thanks

Christian

Am 15.06.2011 15:47, schrieb Willem Jiang:
> Hi Christian,
>
> No, I don't think you can simple replace camel-cxf component with the 
> camel transport for CXF.
>
> camel-cxf component uses the camel component way to integrate the CXF 
> with camel, and camel transport is using CXF transport API to 
> integrate the camel with CXF. You can use the camel transport and 
> camel-cxf together as they integrate the camel and CXF in different 
> level.
>
> cxfbean and the camel transport are more likely used in the server 
> side. If you want to access the WebService by using the proxy way, you 
> still need to use the camel-cxf component.
>
> If you want to build a WebService proxy, camel-cxf component can help 
> you, you can easily do the CBR with help of camel-cxf component.
>

-- 
--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
Talend Application Integration Division http://www.talend.com