wood burning stoves 2.0*
The moose likes Web Services and the fly likes UTF-8 SAX exception- HELP! Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "UTF-8 SAX exception- HELP!" Watch "UTF-8 SAX exception- HELP!" New topic
Author

UTF-8 SAX exception- HELP!

Vladimir Ergovic
Ranch Hand

Joined: Apr 22, 2001
Posts: 63
I am using soap messaging (apache 2.2 and Tomcat4 )in application for transmiting data to another database.
The problem is in charachters which are not English (Croatian). I already try with and without CDATA sections but it doesn't help.
I get following Response:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Client</faultcode>
<faultstring>parsing error: org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x1a) was found in the CDATA section.</faultstring>
...
...
Deadline is tomorow so please help!
Vlad


Vladimir Ergovic
William Brogden
Author and all-around good cowpoke
Rancher

Joined: Mar 22, 2000
Posts: 12675
    
    5
0x1A is NOT a valid unicode character in ANY character set. That is a <ctrl>Z - the eof control code in ascii. You better look at the XML text with a hex editor to find out where the 0x1A is coming from.
Bill


Java Resources at www.wbrogden.com
Vladimir Ergovic
Ranch Hand

Joined: Apr 22, 2001
Posts: 63
Thanks, it was a problem in db2 it wasn't configured as it should be !
Dale Lepine
Greenhorn

Joined: Jan 06, 2003
Posts: 1
Originally posted by Vladimir Ergovich:
Thanks, it was a problem in db2 it wasn't configured as it should be !

What was the problem with the DB2 configuration?
satbir singh
Greenhorn

Joined: Oct 04, 2005
Posts: 1
Originally posted by Vladimir Ergovich:
Thanks, it was a problem in db2 it wasn't configured as it should be !


I am also getting the similar problem. Could you please tell what configurations needs to be done in DB2?
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: UTF-8 SAX exception- HELP!
 
Similar Threads
Could not recognize the SOAP XML Namespace while invoking MessageRouterServlet
Axis rejects int parameter
WAS v6.1 + WS-Security
SOAP Exception : did not recognize the value of HTTP Header SOAPAction:
Server.userException: Exception while executing Client