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=17348>. 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=17348 WSDL2Java creates method >64K [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | ------- Additional Comments From [EMAIL PROTECTED] 2003-07-10 14:32 ------- I respectfully disagree with this resolution. The change which makes WSDL2Java break on large WSDL files was introduced in 1.1. The 1.0 version still works. So much for 'nothing we can do'. Here is the reason. In 1.0 the static type array is initialized each time a SOAP operation is invoked. There is still a 64K limitation, but is controlled by the size of a single operation and is not unreasonable. In 1.1 someone decided that it will be more 'efficient' to combine all these static initializations into a single static call. As a result WSDL2Java breaks when faced with a WSDL file containing fair amount of methods. The WSDL attched to this bug has about 100 methods. After some experimentation I found that I have to break it into 4 parts to go under the limit. Now 20-30 methods is not a huge number to be found in an interface and the limitation imposed by 1.1 is simply not acceptable in production. I am holding off the upgrade to 1.1 untill this bug is fixed or a better SOAP 1.2 package comes along. Sincerely, Jan Hrabowski ([EMAIL PROTECTED])
