cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <>
Subject [jira] Commented: (CXF-2015) Add capability to configure per-request client interceptors
Date Wed, 21 Oct 2009 00:46:59 GMT


Daniel Kulp commented on CXF-2015:

Added properties that can be set on the request context:

     * Some properties to allow adding interceptors to the chain
     * on a per-request basis.  All are a Collection<Interceptor>
     * These are NOT contextual properties (ie: not searched outside the message).
     * They must exist on the message itself at time of Chain creation
    String IN_INTERCEPTORS = Message.class.getName() + ".IN_INTERCEPTORS";
    String OUT_INTERCEPTORS = Message.class.getName() + ".OUT_INTERCEPTORS";
    String FAULT_IN_INTERCEPTORS = Message.class.getName() + ".FAULT_IN_INTERCEPTORS";
    String FAULT_OUT_INTERCEPTORS = Message.class.getName() + ".FAULT_OUT_INTERCEPTORS";
     * As above, but Collection<InterceptorProvider>
    String INTERCEPTOR_PROVIDERS = Message.class.getName() + ".INTERCEPTOR_PROVIDER";

> Add capability to configure per-request client interceptors
> -----------------------------------------------------------
>                 Key: CXF-2015
>                 URL:
>             Project: CXF
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 2.1.2
>            Reporter: Kenny MacLeod
>            Assignee: Daniel Kulp
>             Fix For: 2.2.5
> In its current form, CXF only allows you to configure a given client proxy with a fixed
set of interceptors, which are set up when the proxy object is generated. In some cases, though,
the interceptor stack needs to change on a per-request basis. There is no easy way to do this
in the CXF API short of re-generating the client proxy each time.
> I would like to see a way of wrapping the proxy with additional interceptors which applies
only to the current invocation.  These interceptors would be applies in addition to the statically-configured

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message