Re: [Axis2] Notes on underlying MXparser of OM

[Aleksander Slominski]

jayachandra wrote:
1. The MXParser doesn't seem to support the UTF-8 character set fully.
Japanese XML files weren't parsed properly. In future, this could
throw a serious problem. This can have it's effect on the SOAP message
processing of foreign web services.
 

what is the problem? makes ure to send email about problems to 
http://groups.yahoo.com/group/stax_builders/
and file bug report(s) in bugzilla for StAX RI 
(http://www.extreme.indiana.edu/bugzilla/buglist.cgi?product=STAX)

2. The DTDParser inside MXParser was failing to understand the DTD
declaration line(s) of several (complex?) DTDs. Though this might not
seem as a problem if you look at the SOAP message processing part of
it, but certainly with such a behaviour complete XML infoset support
can not be given to our OM.
 

are you actually testing validating or non-validating parser? 
requirement for non-validating parser are different in regard to DTDs.

moreover DTDs are to be rejected by SOAP processor anyway ...
thanks,
alek
--
The best way to predict the future is to invent it - Alan Kay