cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Greve (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-4958) jaxrs:providers tags seems to be ignored inside jaxrs:client
Date Fri, 12 Apr 2013 12:14:17 GMT

    [ https://issues.apache.org/jira/browse/CXF-4958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630005#comment-13630005
] 

Thomas Greve commented on CXF-4958:
-----------------------------------

I tried the same thing with CXF 2.6.7 -- with the same result.  Looking closely at the code
(which is quite the same as with 2.7.4 -- is this the refactored code?) i see:

When creating the proxy with JAXRSClientFactoryBean in initClient(), the client configuration
is given the SpringBus, the conduit and the interceptors.  Afterwards, within setupFactory()
a new ProviderFactory is created, which in turn creates the new Providers in initJaxbProviders()
(unconditionally and without looking at the bus) and wraps them in ProviderInfo instances.

If this is also a refactored version: which version should i look at?
                
> jaxrs:providers tags seems to be ignored inside jaxrs:client
> ------------------------------------------------------------
>
>                 Key: CXF-4958
>                 URL: https://issues.apache.org/jira/browse/CXF-4958
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 2.7.3, 2.7.4, 2.6.7
>            Reporter: Thomas Greve
>         Attachments: cxf-jackson.xml, cxf-unwrap.xml
>
>
> I try to configure a jax rs proxy based client using cxf.xml to use jackson instead of
the internal JSONProvider.  Alternatively i tried to configure the "depth" parameters without
effect, either.
> This is how i instanciate the client:
>       Service service = JAXRSClientFactory.create(URL, Service.class, "cxf-unwrap.xml");
>       Information information = service.someMethod();
> Inserting JacksonJaxbJSONProvider programmatically works, but i suppose that this is
not the most elegant way.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message