OK, I can suggest two things:
1. Try to experiment with replacing both parameters with a single
MultipartBody parameter and without any annotations. MultipartBody can
let you read individual parts in a type-safe way too. You can also check
its content in the debug mode. You can keep the original signature if
you prefer once the issue is found.
2. Put a breakpoint in JacksonJaxbJsonProvider.isReadable and see if it
is being called.
3. Make sure the default CXF Jettison provider is not registered
(exclude a Jettison dep), though it should not make a difference given
you have a custom Jackson.
4. Try CXF 2.7.18
If you can not make any progress after 1-4, then open a JIRA with a test
case and I'll have a look.
Cheers, Sergey
On 28/08/15 12:08, kanu.emeka wrote:
Q. Does the individual part which carries the json payload have
Content-Type: application/json ?
A - Yes it does. Plus I also tried setting the type in @Multipart annotation
as well.
Q. If yes - can JacksonJaxbJsonProvider convert it, is Status type a JAXB
bean ?
Yes and yes. In previous iterations, I had this method with only the
StatusUpdateType and no attachment. In that instance, the @Consumes
contained only application/json, and it all worked fine.
This is a new iteration, where I am attempting to add an attachment, and as
such have made everything @Multipart as specified by the CXFRS
documentation.
Yes Jackson worked fine, and has worked fine in every other service that I
have registered as part of my APIs.
--
View this message in context:
http://cxf.547215.n5.nabble.com/JAX-RS-form-reading-I-m-stumped-tp567915p5760555.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
