[jira] Closed: (CXF-379) WS-Policy: Client side interceptor chain setup depending on binding operation's effective policy

["Andrea Smyth (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CXF-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrea Smyth closed CXF-379.
----------------------------


> WS-Policy: Client side interceptor chain setup depending on binding operation's effective policy
> ------------------------------------------------------------------------------------------------
>
>                 Key: CXF-379
>                 URL: https://issues.apache.org/jira/browse/CXF-379
>             Project: CXF
>          Issue Type: Task
>          Components: WS-* Components
>            Reporter: Andrea Smyth
>         Assigned To: Andrea Smyth
>
> Given the binding operation, determine the effective policy and use the AssertionInterceptorProvider API to determine which interceptors are required to support a policy alternative.
> First look at preconfigured interceptors: if with these one of the alternatives is supported, choose it (user configuration takes precedence).
> Need to include transport and existing interceptors in checklist (cast to Assertor).
> Choose alternative for which the minimum numner of interceptors need to be added. Or else have the interceptors provided by the AssertionInterceptorProvider implement an interface that determines the cost of an interceptor being added dybamically and or executed in the chain, and choose the alternative so as to minimise cost.
> Initially however assume one alternative only.
> Cache the binding operation specific interceptor chains/interceptors for efficiency (allow recombination of chain but avoid instantiating interceptors on a per-invocation basis).

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