DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19327>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19327 Character entities are escaped to aggressively ------- Additional Comments From [EMAIL PROTECTED] 2003-07-07 16:35 ------- I have started to migrate (copy and paste) a few Xerces classes to ensure proper umlaut encoding within Axis (EncodingInfo, EncodingMap, Encodings, Printer). Apart from migrating those classes I tried to achieve the following goals: 1. Support other encoding styles than UTF-8/ISO-8859-1. 2. Make encoding configurable through server-config.wsdd settings, use UTF-8 as default. 3. Provide static, request dependant (ThreadLocal) access to the current encoding name/ String encoder within Axis. 4. Support two encoding strategies: a) Fixed encoding. b) Client call dependant response encoding. Apart from some questions "implementing" 1 to 4a is pretty straight forward. A few questions: Do you think 4b could be useful at all? Looks like a major change for axis. The Xerces Encoder makes use of an internal writer which inherits usage of an OutputStream. This is pretty expensive. Also the current implementation is stateful and not thread safe. Therefore I was about to provide a dedicated StringEncoder for every request using ThreadLocals, similar to AxisEngine. getCurrentMessageContext(). Do you think this is OK? If yes, is a static method in AxisEngine a proper location to access the current StringXmlEncoder? The Xerces encoder uses sun.io.CharToByteConverter!? Currently I do have to deal with UnsupportedEncodingExceptions and low level IOExceptions within the XML Encoder. In case of an UnsupportedEncodingException I use UTF-8 as fallback (and complain about the wrong encoding name). This would happen once during initialization. However it is possible to run into IOExceptions for every String->XML encode. During SOAP Response Envelope Encoding I could throw a SOAP Fault. What should I do while encoding SOAP Request or AxisFault elements?
