cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <>
Subject [jira] [Resolved] (CXF-5457) Provide access to BindingProvider in case of using Blueprint proxy injection
Date Fri, 17 Jan 2014 20:31:21 GMT


Daniel Kulp resolved CXF-5457.

       Resolution: Won't Fix
    Fix Version/s: Invalid

Not something that WE can do anything about.   This is completely within the blueprint implementations
control and whether it completely hides the actual implementation and such.

> Provide access to BindingProvider in case of using Blueprint proxy injection
> ----------------------------------------------------------------------------
>                 Key: CXF-5457
>                 URL:
>             Project: CXF
>          Issue Type: Improvement
>          Components: JAX-WS Runtime
>    Affects Versions: 2.7.8
>            Reporter: Andrei Shakirin
>             Fix For: Invalid
> The issue is described in [ARIES-1140 |].
> Problem is that in case if generated service interface is injected as jax-ws client proxy
using Blueprint, this proxy object implements only business interface and not BindingProvider
> Because of this it is necessary to implement custom code to propagate context values
(for example using ThreadLocal) instead using of specified jax-ws way. Strongly saying, injected
proxy is not jax-ws compatible, because spec requires to implement BindingProvider for all
> 4.2
> The BindingProvider interface represents a component that provides a protocol binding
for use by clients, it is implemented by proxies and is extended by the Dispatch interface.
> From the other side, Blueprint spec requires that proxy implements one and only one interface
declared in the service.
> Perhaps we can provide kind of proprietary API in CXF that retrieves BindingProvider
for given proxy. Suggestions, ideas and comments are welcome. 

This message was sent by Atlassian JIRA

View raw message