[jira] [Created] (CXF-5457) Provide access to BindingProvider in case of using Blueprint proxy injection

["Andrei Shakirin (JIRA)" <ji...@apache.org>]

Andrei Shakirin created CXF-5457:
------------------------------------

             Summary: Provide access to BindingProvider in case of using Blueprint proxy injection
                 Key: CXF-5457
                 URL: https://issues.apache.org/jira/browse/CXF-5457
             Project: CXF
          Issue Type: Improvement
          Components: JAX-WS Runtime
    Affects Versions: 2.7.8
            Reporter: Andrei Shakirin


The issue is described in [ARIES-1140 | https://issues.apache.org/jira/browse/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 interface.
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 proxies:
4.2 javax.xml.ws.BindingProvider
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
(v6.1.4#6159)