Illegal XML character revisit and ways to handle the exception

[Liu, Scott]

Hi, All,   Searching from the mailing list and I have found several past entries about the illegal XML character topic but none of them have given a definite answer. I would like to know how people are handling them in their applications. My own example is due to the fact that there are delimiters like Unicode \u0005 in my data which causing the exception like listed below.   AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException faultSubcode: faultString: org.xml.sax.SAXParseException: Illegal XML character  faultActor: faultNode: faultDetail: {http://xml.apache.org/axis/}stackTrace: org.xml.sax.SAXParseException: Illegal XML character  at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3182) at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3176) at org.apache.crimson.parser.Parser2.surrogatesToCharTmp(Parser2.java:24 93) at org.apache.crimson.parser.Parser2.maybeReferenceInContent(Parser2.jav a:2427)   Axis server run fine and converts the Unicode to its entity reference like “&#xN;” and it does not throw any error. The problem is on the client side which it failed. My question is that is there a way to tell the client Sax parser to ignore this and leave it to the client application to handle “&#xN;” as it fits.   Any suggestion is greatly appreciated.   Thanks,   Scott