On Wednesday, October 26, 2011 2:02:54 PM Conficio wrote: > Thanks Dan, > for your comment. I agree if feed invalid XML it should complain. > > However in my situation, I'd think that if I use some Java bean with a > String attribute and CXF on the server and client side, the the marshaling > and un-marshaling does take care of escaping characters that are not allowed > in XML.
The point is that there are certain characters that CANNOT be represented in XML at all, escaped or not. CXF DOES escape the characters that are valid. (well, woodstox does) However, if the character cannot be stuck in XML, escaped or otherwise, it needs to throw an exception. > What surprises me here is that only the client does complain with the > exception, but the server happily puts out the invalid XML. Possibly a different XML parser. Woodstox is pretty strict about being compliant. Other parsers might not be. Dan > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/String-with-Ctrl-Character-marshalling-unma > rshalling-error-tp4924570p4941165.html Sent from the cxf-user mailing list > archive at Nabble.com. -- Daniel Kulp [email protected] http://dankulp.com/blog Talend - http://www.talend.com
