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=22360>. 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=22360 WSDL2Java throws emitter time out exception even though WSDL is on local disk ------- Additional Comments From [EMAIL PROTECTED] 2003-08-13 18:23 ------- I absolutely agree that at runtime the xml parser used to read soap messages should be a JAXP-provided parser chosen by the deployer. There's no good reason to change that. The code generation stuff, however, is another matter. There are clearly advantages to changing it (better performance, reuse of existing, well written code that specifically addresses the req't of understanding XML schema). The big obstacle is (1) emitter api backward compatibility; (2) making xerces a deployment requirement for users who expect to process dynamic wsdl. Given the issues with the current implementation, I think #2 is a sellable concept. #1 is the one that worries me -- I simply don't know how many people are depending on the current representation of schema types via the emitter framework. It sure would be nice to hear from those folks, if they exist.
