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 Throw an error when wrapped and non-wrapped WSDL are mixed [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Java types not generated if |Throw an error when wrapped |opertion name matches |and non-wrapped WSDL are |element name |mixed ------- Additional Comments From [EMAIL PROTECTED] 2003-01-06 17:07 ------- The --nowraped flag was added explicitly to avoid cases like this where the 'autosensing' mode caused trouble. I would agree that an enhancement to throw an error when we encounter 'mixed mode' WSDL would be a nice thing to do. I am changing the summary to indicate this is the problem. The error should direct the user to the --nowrapped flag. Wrapped mode is a hack, but its a hack that supports a high percentage use case (.NET) in a way that make life easier for developers (ie. rpc style arguments instead of a single Bean in/out).
