Thanks Glen and Sergey. That solved the escape issue I run into. but with
Jackson provider it seems lost other features that cxf json provider
provided.
for example, I have the a jaxb annotated A class that has a list of fields
with one Object field:
@XmlRootElement
@XmlAccessorType(XmlAccessType.FIELD)
public class A {
String x;
@XmlAnyElement(lax=true)
Object obj;
...
with cxf json provider, I can get it work with both xml/json. most
importantly I can assign the obj to different class such as B1.class or
B2.class at run time and get the json marshaling results correctly (except
the escape issue):
{"x":"x value","b1":{"b1_id":"b1_id value"}} or {"x":"x
value","b2":{"b2_id":"b2_id value"}}
using jackson provider it won't work with json unless the @JsonProperty
being put for every field and I also lost the nice run time binding, instead
I got "obj" all the time:
{"x":"x value","obj":{"b1_id":"b1_id value"}} or {"x":"x
value","obj":{"b2_id":"b2_id value"}}
thanks again for the help,
--
View this message in context:
http://cxf.547215.n5.nabble.com/forwardslash-being-escaped-from-json-response-tp5727304p5727380.html
Sent from the cxf-user mailing list archive at Nabble.com.
