[
https://issues.apache.org/jira/browse/CXF-4958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13627971#comment-13627971
]
Thomas Greve commented on CXF-4958:
-----------------------------------
I used the depth parameters as an example, as i found the code reading them
(but not finding them lacking a context). What i really intend is in fact to
read a "Jackson style" REST service (unwrapped root), which throws an exception
expecting the root name ("information" in my case). This exception always
involves the cxf JSONProvider, even with the "jackson" config attached.
When i programmatically enforce the Jackson provider, the service can be read;
when i set the "supportUnwrapped" property directly in the provider instance
during a debugging session, the service can be read properly as well.
When i use the jettison config example at
http://cxf.apache.org/docs/jax-rs-data-bindings.html (which at least contains a
complete configuration example :-) (analogously) it does not have any effect
either.
BTW: the code is part of a simple JUnit test, so there is no pre-existing
spring container. The whole of the spring environment is started when the
service client is instantiated.
> jaxrs:providers tags seem 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
> 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
