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 17:24 ------- Rick, Just to be sure that I understand the issue -- is that because we don't want to have a runtime dependency on this-or-that xml parser implementation? I imagine that everyone would be OK if it were a build-time dependency, but I can understand not wanting to *have* to use xerces for all XML tasks. And since Axis does support wsdl interpretation at runtime, it's not possible to use xerces for that if our policy is "no xerces at runtime." With all of that said, I think it's fair to say that Axis' runtime wsdl interpreting services are not really usable for large schemas. This is not a slam or a dig at anyone -- I'm simply pointing out that very few applications can afford to spend 10+ minutes grinding over wsdl at runtime. So, we should probably tell people that they shouldn't try to use complex schemas in dynamically interpreted wsdl. While this is a regrettable limitation, it's not a ridiculous one, as it'd be pretty hard to write an application that could actually do something meaningful with a very complex dynamically defined web service. The third way, such as it is, would be to build a xerces-based, development- time only, code generator for Axis and make it an add-on. I actually wrote one last fall when I thought I needed fail-fast capabilities in generated beans (i.e. setters that throw exceptions when given parameters that don't match the schema facets). It's crufty and looks *only* at the schemas (not the wsdl itself), but it did produce working code in about 1/100th the time it took WSDL2Java (AFAICR). If there's interest, I'll see if my boss is willing to let me contribute it back to the community, and I'll even spend some time working to make it useful for someone other than me. ;)
