← Prev in month
← Prev in thread
Parsing Kanji (Japanese) characters...
Hi - Is the SAX Parser able to handle Kanji characters? Any help/pointers are appreciated. I am trying parse and document in Kanji characters and get the following stack trace: java.rmi.RemoteException: EJB Exception: ; nested exception is: com.citicorp.WebTicketRouter.BusinessServices.DealTicketManagementServic es.DealTicketManagerServiceException: nested exception is: org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x1b) was found in the element content of the document. org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x1b) was found in the element content of the document. at weblogic.apache.xerces.framework.XMLParser.reportError(XMLParser.java:12 92) at weblogic.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError( XMLDocumentScanner.java:613) at weblogic.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.di spatch(XMLDocumentScanner.java:1336) at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumen tScanner.java:399) at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:1138) at weblogic.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImp l.java:203) at weblogic.xml.jaxp.RegistryDocumentBuilder.parse(RegistryDocumentBuilder. java:144) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:86) at com.citicorp.WebTicketRouter.BusinessServices.DealTicketManagementServic es.DealTicketManagerEJB.getDocumentElement(DealTicketManagerEJB.java:122 5) Nizar Hirani (416) 947-5421 This message may contain confidential, proprietary or legally privileged information. If you are not the intended recipient, please notify the sender immediately and delete the message from your system. You should not copy or use it for any purpose, nor disclose its contents to any other person. Also, if you are not the intended recipient, you are hereby notified that you are not authorized to review the contents of this email and that any dissemination, distribution or copying of this message is strictly prohibited.
← Prev in month
← Prev in thread