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=13883>. 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=13883 DII WSDL processing doesn't deal with wrapped mode Summary: DII WSDL processing doesn't deal with wrapped mode Product: Axis Version: 1.0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: WSDL processing AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] If you try to use the DynamicInvoker to get at what you'd think might be a simple service, the doc/lit "echoString" from the recent interop tests, you'll find that you fail rather badly. This is because the WSDL processing code in the DynamicInvoker doesn't cope with wrapped mode services. Note that the code in Service.java which processes WSDL doesn't deal with this either. We could either extend the code in Service to cope with this (IMHO, DynamicInvoker should just be using our DII code, rather than trying to do the same work again itself), or we could try to resolve the fact that we have two different WSDL parsing systems (one for WSDL2Java, one for DII) which could perhaps profitably be merged into one (WSDL -> metadata which can either be used directly by DII or converted to Java source). (the WSDL URL is http://mssoapinterop.org/asmx/xsd/round4XSD.wsdl)
