[
https://issues.apache.org/jira/browse/CXF-4958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13631722#comment-13631722
]
Sergey Beryozkin edited comment on CXF-4958 at 4/15/13 1:43 PM:
----------------------------------------------------------------
I have updated one of the tests, see this commit to CXF 2.6.8-SNAPSHOT:
http://svn.apache.org/r1468055
The (JAXB) provider is configured within jaxrs:client and picked up properly,
without it the updated test code fails (and with it the test fails unless the
code gets updated as per this commit).
What exactly is different in your case - can you provide a basic Maven-based
project ?
Cheers
was (Author: sergey_beryozkin):
I have updated one of the tests, see this commit to CXF 2.6.8-SNAPSHOT:
http://svn.apache.org/r1468055
The (JAXB) provider is configured within jaxrs:client and picked up properly,
without it the updated test code fails (and with it the test fails unless the
code gets updated as per this commit).
What exactly is different in your case - can you provide a basic Maven-based
project ? Have you actually tried CXF 2.6.7 ?
Cheers
> 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
