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=15533>. 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=15533 Java types not generated if opertion name matches element name [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2002-12-19 16:31 ------- Don't you mean unwrapped? The Schema is being unwrapped into the individual parameters. I don't think stumbled across it is the right term as I use several toolkits including Axis, .Net and BEA, but whatever. I still have problems with this i) You have different generation behaviour depending on the operation names. This seems fragile to me. Wouldn't it be better to always do things one way and then provide a flag or flags to to 'wrapped' or unwrapped ii) If I mix and match styles in the WSDL then I get compile errors, then for the types I wan't 'wrapped' I don't get any types generated. In a simple case the porttype class has two methods one that takes two doubles and returns a diuble (unwrapped?) and one that takes an AddRequestType and returns an AddResponseType (wrapped), as defined by the WSDL. However the AddResponseType and AddRequestType Java classes aren't being generated. It seems that as soon as the tool discovers an unwrapped operation it stops type generation. If you want sample WSDL for this I'm happy yo provide it.
