The latest version of CXF ? That would explain it why having Jettison
was affecting it.
In earlier CXF if the custom provider was matching then the default
providers were not checked. It proved to be not spec compliant, as the
spec does require both default and custom providers being considere
Make sure please it is targeted to the users list.
Can you confirm you provider is not called by debugging ? Example,
override isReadable/isWriteable and put breakpoints there ?
The default jettison provider can only be called if you have jettison
available on the classpath - make sure it is not
Well, is your custom provider selected ?
Looks like you have 2 json providers. If you keep a custom provider
only, what happens ?
Sergey
On 18/08/15 20:40, craigrs84 wrote:
I have the following setup, I'm trying to use Jackson Json provider with
custom settings applied.
However whenever I conn
