...
8. In some cases the matching sub-resource locators will be dropped to precisely meet the current JAX-RS matching algorithm text, please see CXF-5650 for more information. Use a new "keep.subresource.candidates" property to support the existing application if needed.
CXF 3.1.2 Provider Sorting Changes
Starting from CXF 3.1.2 custom MessageBodyReader (MBR) and MessageBodyWriter (MBW) providers are sorted together with default providers.
Before CXF 3.1.2 if a custom MBR or MBW matches the read or write selection criteria, example, if MBR Consumes matches Content-Type and its isReadable() returns true, then
the default providers are not even checked. The specification however does let the custom providers be selected only if no higher priority matching default provider is available.
For example, suppose you have a custom StringReader which is not typed by String but by Object. In this case the default provider which is typed by String wins. To have the custom String provider winning one needs to type it by String. Check the specification or ask at the users list for more details
From CXF 2.6.x to CXF 2.7.x
...