Subjects
Home
VOTE Move XML Commons to Xerces
Commented: (XERCESJ 589) Bug with pattern restriction on long strings
: Xerces J 2 8 1 Release on Wednesday, September 13th
: Xerces J 2 9 0 Release on Wednesday, November 22nd
Commented: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1178) Error getting prefix for an attribute with no n
Updated: (XERCESJ 1244) XMLSchemaValidator does not contribute element 's
Some consideration about the xerces DOM implementation
Updated: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1227) Poor performance / OutOfMemoryError for sequenc
retain exception stack traces
Updated: (XERCESJ 1193) NPE or hang when parsing using the "continue afte
Future of NekoHTML
Commented: (XERCESJ 1203) NPE in XMLDTDProcessor
DOM Level 3 APIs for Xalan J and a new Xalan release (2 7 1)
: xml commons external 1 3 04 Release on Wednesday, November 22nd
Commented: (XERCESJ 1247) Incorrect location information on SAX when usin
XInclude exceptions how to mirror Xerces J functionality into Xerces C++?
First proposal on SoC project "Add support for the StAX (JSR 173) cursor API
: xml commons resolver 1 2 Release on Wednesday, November 22nd
Typo in RangeToken java Please check
Validator features
java lang ClassCastException when adopting Node
using the org apache xerces impl xs identity package
Updated: (XERCESJ 1257) buffer overflow in UTF8Reader for characters out
Problem with ref attributes and schema validation
Updated: (XERCESJ 122) XMLSchemaValidator does not contribute element 's d
Performance problem under load Xerces with Weblogic 9 x
remove ignored memory allocation
Commented: (XERCESJ 1177) SAXXMLStreamReader doesn 't always report namesp
Commented: (XERCESJ 977) Null pointer exception during DOM parsing
Commented: (XERCESJ 1197) Code cleanup for org apache xml serialize
Commented: (XERCESJ 1201) Initial contribution for StAX Event API
Updated: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special c
Commented: (XERCESJ 1199) SAXXMLStreamReader should attempt to register a
Commented: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special
Updated: (XERCESJ 589) Bug with pattern restriction on long strings
StackOverflow
xerces Range unnecessarily not garbage collectable if not detached
Updated: (XERCESJ 1178) Error getting prefix for an attribute with no nam
Bug in xs:redefine
Commented: (XERCESJ 1204) Can not set XMLEntityResolver for LSParser
Updated: (XERCESJ 1253) Prototype for SoC2007 project "Add support for th
Updated: (XERCESJ 1259) Add SteamFilter Function to SoC2007 project "Add
Assigned: (XERCESJ 444) SAXException thrown by EntityResolver is reported
Google Summer of Code 2007
Xerces J and XInclude relative path issue
Assigned: (XERCESJ 206) Stack overflow when using a schema validation
Commented: (XERCESJ 1215) Restrictions involving two levels of substituti
Closed: (XERCESJ 1203) NPE in XMLDTDProcessor
non overriding equals methoda
Resolved: (XERCESJ 1079) invalid value returned for TOTALDIGITS facet in
Xerces AS3 port
Updated: (XERCESJ 325) Regular Expression; Pattern "| " clause order de
Updated: (XERCESJ 1196) Javadoc generation fails on Java SE 5 0
Closed: (XERCESJ 1202) DTD validation on XIncluded documents when the sch
Created: (XERCESJ 1124) Nonspecific schema error message
a bug in xerces
Updated: (XERCESJ 1201) Initial contribution for StAX Event API
Closed: (XERCESJ 1254) Empty uris in targetNamespace attribute not report
Links
Home
Oracle database error code
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
problem with DOM and Encoding

problem with DOM and Encoding

2004-02-25       - By Markus Jais

hi

I have 2 different methods for outputting a DOM Tree:


Methode 1: (DOM 3 / Xerces 2.4)
===========
public String toXML2() throws RPCException
��������{
����������������String��������������ret�=�"UNO";
����������������DOMWriter�writer�=�null;
����������������
����������������try�{
������������������������writer�=�((DOMImplementationLS)this.implementation)
.createDOMWriter();
������������������������writer.setEncoding("ISO-8859-1");
������������������������ret�+=�writer.writeToString(document);
����������������}�catch�(DOMException�domex)�{
������������������������;
����������������}
����������������return�ret;
����������������
��������}
��������

Methode 2: (JAXP + TRAX with Xerces 2.4)
============
public String toXML() throws RPCException
��������{
����������������String�ret�=�"DOS";
����������������try�{
������������������������TransformerFactory�transFactory�=�TransformerFactory
.newInstance();
������������������������Transformer�transformer�=�transFactory.newTransformer();
������������������������Source�input�=�new�DOMSource(document);
������������������������StringWriter�strWriter�=�new�StringWriter();
������������������������Result�output�=�new�StreamResult(strWriter);����
������������������������transformer.setOutputProperty(OutputKeys.ENCODING,�"ISO
-8859-1");
������������������������transformer.transform(input,�output);
������������������������ret�+=�strWriter.toString();
������������������������try�{
��������������������������������strWriter.close();
������������������������}�catch�(IOException�ex)�{
��������������������������������throw�new�RPCException("Error�closing�String
�Writer");
������������������������}
������������������������return�ret;
������������������������
����������������}�catch�(TransformerConfigurationException�ex)�{
������������������������;
����������������}�catch�(TransformerException�ex)�{
������������������������;
����������������}
����������������
��������}




both return a string
method 1 turns "M�nchen" into:��
M�nchen

and method 2 into
M�nchen

(If your news reader does not display german umlauts: in HTML you would
write "München")


it seems that both encodings are wrong and also different.
this is weird. I also did a

export LANG=de_DE

no changes although within my JBOSS message driven bean it works with
this variable set.

I have Suse Linux 8.2 and java version "1.4.2_03"


any ideas what's wrong here ?



Markus
--
Markus Jais
Software Developer
GMX GmbH
Riesstra�e 17, 80992 M�nchen
Phone: +49 89 14 339-514
mailto:mjais@(protected)
http://www.gmx.de



---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)