cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergey Beryozkin <sberyoz...@gmail.com>
Subject Re: Per Client interceptor
Date Thu, 06 Feb 2014 21:23:55 GMT
Hi
On 06/02/14 19:17, Daniel Kulp wrote:
>
> There are a couple of options:
>
> 1) In your interceptor itself, detect if it’s client side or server side and act appropriately.
 We have a MessageUtils.isRequestor(msg) method that will return true if we’re on the client
(requestor) side.
>
> 2) Implement a ClientLifecycleListener that would only add the interceptor at creation.
 It wouldn’t apply to servers then.
>

I've been thinking at the introduction of a new @Scope (sub) annotation 
too, haven't had the time to look more into it, but if introduced it can 
offer another option,

Thanks, Sergey

>
>
> Dan
>
>
>
> On Feb 6, 2014, at 8:28 AM, Thomas Manson <dev.mansonthomas@gmail.com> wrote:
>
>> Hi,
>>
>> I've build a library that calls a set of webservices (provided by the
>> same application) with CXF.
>>
>>   I've my own interceptor that is attached to the Bus :
>>
>> <cxf:bus>
>>   <cxf:features>
>>     <p:policies />
>>     <cxf:logging />
>>   </cxf:features>
>>   <cxf:outInterceptors>
>>     <ref bean="AMXBPMSecurityWSS4JOutInterceptor" />
>>   </cxf:outInterceptors>
>> </cxf:bus>
>>
>> My library is included in a webapplication, that needs to consume
>> another webservice (different from the one used by my library).
>>
>> with my interceptor I trap all outgoing soap call, so it interfere
>> with the webapp soap call, and make them fail for security reasons.
>>
>> How can I configure my interceptor only for a set of clients, so that
>> my library is agnostic and do not interfere with other soap call?
>>
>> All example I've found attach the interceptor to the bus.
>>
>> Regards,
>> Thomas.
>


-- 
Sergey Beryozkin

Talend Community Coders
http://coders.talend.com/

Blog: http://sberyozkin.blogspot.com

Mime
View raw message