Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of willem.jiang@gmail.com
 designates 209.85.142.188 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:x-enigmail-version:content-type
         :content-transfer-encoding;
        b=aP320Yn+gaqwTEkHW2NMl9T6AH8cxaSeIt6lQVl4CTdIXL4eNE7GNdjP90Pm4a5Kb1
         Cm5/UvfO1qlDbZcq8tST6prFVbSsT8fsCoOASOPCuixjgdDwRPAdYdsYFvaWEZiZbrpP
         PyRDqC8DWQNZ/3Ci1/MNW7imKmbS2QiHAwWmg=
Message-ID: <4975C55C.1000907@gmail.com>
Date: Tue, 20 Jan 2009 20:36:44 +0800
From: Willem Jiang <willem.jiang@gmail.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: users@camel.apache.org
Subject: Re: Definining interceptors in camel-cxf
References: <49749850.50909@bull.net>
 <e396dae20901190852g2c2a171apf8cbed17d42ad937@mail.gmail.com>
 <4975A68F.4080402@bull.net>
In-Reply-To: <4975A68F.4080402@bull.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

Hi

You can set the interceptors into cxf bus[1], then all the CXF endpoints
create by CAMEL will use them.
[1]http://cwiki.apache.org/CXF20DOC/bus-configuration.html

Willem

S. Ali Tokmen wrote:
> Hello, Pawel
> 
> Thank you for this quick response. I now have another issue: I would
> actually be interested in defining these properties globally, i.e. for
> all CXF endpoints created by CAMEL. This way, people programming the
> routes would only use CXF URLs and not create the CXF beans by hand.
> 
> Thank you
> 
> S. Ali Tokmen
> savas-ali.tokmen@bull.net
> 
> Office: +33 4 76 29 76 19
> GSM:    +33 66 43 00 555
> 
> Bull, Architect of an Open World TM
> http://www.bull.com
> 
> 
> 
> Pawel Jasinski a �crit :
>> Hi,
>>
>> here is a snipped from the camel-context where wss4j is defined as
>> interceptor:
>>
>>   <cxf:cxfEndpoint id="consumerEndpoint"
>>     address="http://localhost:9001/SoapContext/SoapPort/consumer"
>>     wsdlURL="wsdl/consumer/consumer.wsdl"
>>     serviceClass="org.example.consumer.Consumer"
>>     endpointName="s:consumerSOAP"
>>     serviceName="s:consumer"
>>     xmlns:s="http://www.example.org/consumer/">
>>
>>     <cxf:inInterceptors>
>>     <!-- request consumer => esb -->
>>       <bean class="org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor">
>>         <constructor-arg>
>>           <map>
>>             <entry key="action" value="SAMLTokenUnsigned Timestamp
>> Signature Encrypt" />
>>
>>             <!-- signature -->
>>             <entry key="user" value="" />
>>
>>             <!-- alias from the keystore to decrypt message -->
>>             <entry key="signaturePropFile"
>> value="META-INF/identity.properties" />
>>
>>             <!-- encryption -->
>>             <entry key="decryptionPropFile"
>> value="META-INF/wss-bus.properties" />
>>             <entry key="passwordCallbackClass"
>> value="org.example.common.PasswordHandler" />
>>           </map>
>>         </constructor-arg>
>>       </bean>
>>       <bean class="org.example.common.SAMLInterceptor">
>>       </bean>
>>     </cxf:inInterceptors>
>>     <cxf:outInterceptors>
>>      ....
>>
>>     </cxf:outInterceptors>
>> </cxf:cxfEndpoint>
>>
>> I hope this helps.
>> -- Pawel
>>
>>
>> On Mon, Jan 19, 2009 at 4:12 PM, S. Ali Tokmen
>> <savas-ali.tokmen@bull.net> wrote:
>>  
>>> Hello
>>>
>>> In CXF, one can define a serioes of interceptors, inbound and
>>> outbound, for
>>> doing many actions. Our implementation defines some Processor
>>> interceptors
>>> for handling security-related tasks (namely, serializing and
>>> deserializing
>>> Security Contexts).
>>>
>>> In CXF-Spring, this is done using the jaxws:inInterceptors tag in the
>>> jaxws:endpoint definition.
>>>
>>> Now, I would like to integrate this mechanism into CAMEL... And the
>>> question
>>> is: how can we define CXF interceptors in CAMEL? Programmatic definition
>>> works perfectly for me -if CAMEL for example defines a default CXF
>>> bus for
>>> itself, getting a reference to it and adding my interceptors for all
>>> camel-cxf endpoints would be great.
>>>
>>> Thanks
>>>
>>> -- 
>>>
>>> S. Ali Tokmen
>>> savas-ali.tokmen@bull.net
>>>
>>> Office: +33 4 76 29 76 19
>>> GSM:    +33 66 43 00 555
>>>
>>> Bull, Architect of an Open World TM
>>> http://www.bull.com
>>>
>>>
>>>
>>>     
>>
>>
>>
>>   
> 
>