[
https://issues.apache.org/jira/browse/CXF-6654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David J. M. Karlsen updated CXF-6654:
-------------------------------------
Description:
Our jaxrs:server is configured with
{noformat}
<jaxrs:providers>
<ref bean="jacksonJaxbJsonProvider" />
</jaxrs:providers>
{noformat}
but still jettison was used for unmarshalling incoming requests (which failed
because they are jaxbbeans).
Excluding jettison which was coming in as a transitive dependency from
http://repo1.maven.org/maven2/org/apache/camel/camel-xstream/2.16.0/
fixed it.
This did not cause a problem on cxf 3.1.1, but would fail on 3.1.2 and 3.1.3
was:
Our jaxrs:server is configured with
{code:xml}
<jaxrs:providers>
<ref bean="jacksonJaxbJsonProvider" />
</jaxrs:providers>
{code:xml}
but still jettison was used for unmarshalling incoming requests (which failed
because they are jaxbbeans).
Excluding jettison which was coming in as a transitive dependency from
http://repo1.maven.org/maven2/org/apache/camel/camel-xstream/2.16.0/
fixed it.
This did not cause a problem on cxf 3.1.1, but would fail on 3.1.2 and 3.1.3
> Jettison sneaks in as provider although jackson is registered
> -------------------------------------------------------------
>
> Key: CXF-6654
> URL: https://issues.apache.org/jira/browse/CXF-6654
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
> Affects Versions: 3.1.2, 3.1.3
> Reporter: David J. M. Karlsen
>
> Our jaxrs:server is configured with
> {noformat}
> <jaxrs:providers>
> <ref bean="jacksonJaxbJsonProvider" />
> </jaxrs:providers>
> {noformat}
> but still jettison was used for unmarshalling incoming requests (which failed
> because they are jaxbbeans).
> Excluding jettison which was coming in as a transitive dependency from
> http://repo1.maven.org/maven2/org/apache/camel/camel-xstream/2.16.0/
> fixed it.
> This did not cause a problem on cxf 3.1.1, but would fail on 3.1.2 and 3.1.3
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
