Hi,
if you open the attached file with an editor that let you see the hex
code of the files, for example ghex2 in linux, you'll see that before
the string
denominaciones de origen espa
there's a 0x1c byte that's the one that causes the exception. Removing
this byte there's a further failure
encoding just because you demarcate some block of characters
inside a CDATA section.
- Wing Yew
-Original Message-
From: Bartolomeo Nicolotti [mailto:bnicolo...@siapcn.it]
Sent: Tuesday, August 25, 2009 2:15 AM
To: user@xmlbeans.apache.org
Subject: Re: Illegal XML character: 0x1c inside
Hi,
we do the same, we use have the attached file in a string, having POSTed
it with
int org.apache.commons.httpclient.HttpClient.executeMethod(HttpMethod
method) throws IOException, HttpException
and then we do XMLObject.parse, as you can see also from the call
stack:
Hi,
we're receiving xml from a supplier encoded in ISO-8859-1, but some tags
body are encoded with UTF-8, but they are surrounded with CDATA, so that
strange encodings, like 0x1c character shouldn't be a problem to the
parser, as said here:
http://www.w3schools.com/xmL/xml_cdata.asp
We've built
I've seen similar when working with content retrieved from URLs. What I
found was the problem wasn't in the content of the xml, but in some
additional data that was passed along prior to the xml payload I wanted. My
workaround to this was to use some IO Stream APIs to read the content into a
5 matches
Mail list logo
