You only show one "<xs:schema" element under <applications><grammars>? I had two and one was in the default namespace (xmlns="") If you only have the one: xmlns:tns="http://www.example.com/model/JsonDemo" then your issue is not manifesting like the one we had is.
I should mention we are using an older flavor of cxf - 2.5.x. Anyway just thought I'd throw that at you in case it sparked anything... Good luck, Cheers -----Original Message----- From: jbright [mailto:[email protected]] Sent: Tuesday, January 22, 2013 10:46 PM To: [email protected] Subject: RE: JacksonJsonProvider not working with CXF Jax-RS Clint Dovholuk wrote > Not sure if it's relevant but I had this precise issue recently when > the service's data objects were in two different namespaces. When I > hit our _wadl it had two different 'schemas' in the /application/grammars > section. > This worked just fine for xml but broke my json and the only > resolution I had found was to prevent the service from having two schemas. I did check the _wadl and this is what available there, I'm not clear on what you are referring as two different schemas ; <application xmlns="http://wadl.dev.java.net/2009/02" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:prefix1="http://www.example.com/model/JsonDemo"> *<grammars>* <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://www.example.com/model/JsonDemo" attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://www.example.com/model/JsonDemo"> -- View this message in context: http://cxf.547215.n5.nabble.com/JacksonJsonProvider-not-working-with-CXF-Jax-RS-tp5721842p5722035.html Sent from the cxf-user mailing list archive at Nabble.com.
