You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2014/01/17 21:31:21 UTC

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

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

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: 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
>             Fix For: Invalid
>
>
> 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.5#6160)