Hello,
Bug found in org.dom4j.io.XmlParser.pushURL around line 3614 (can't tell exactly where
anymore because I've tinkered with it).
// RFC 2376 sez MIME text defaults to ASCII, but since the
// JDK will create a MIME type out of thin air, we always
// autodetect when there's no explicit charset attribute.
if (temp < 0)
encoding = null; // autodetect
else {
temp = encoding.indexOf ('=', temp + 7);
encoding = encoding.substring (temp); // <-- BUG
That last line should read:
encoding = encoding.substring ( temp + 1 ); // OK
I had a JSP page outputting Japanese XML with a page
contentType="text/xml;charset=UTF-8", and kept getting unsupported encoding exceptions
for "=UTF-8" when I tried to consume the service with XTags (which is built upon
dom4j).
I've never submitted a bug report to dom4j before. Can I just assume it will be
fixed, or can I do it myself?
Cheers,
James Dodd
PS Mr Strachan, it would be great to hear what you're up to these days!
_______________________________________________
dom4j-dev mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dom4j-dev
