You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-dev@axis.apache.org by bu...@apache.org on 2003/10/08 18:24:24 UTC

DO NOT REPLY [Bug 23677] New: - doc/lit unusable for WSDL which does not follow Axis naming conventions

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=23677>.
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=23677

doc/lit unusable for WSDL which does not follow Axis naming conventions

           Summary: doc/lit unusable for WSDL which does not follow Axis
                    naming conventions
           Product: Axis
           Version: current (nightly)
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Serialization/Deserialization
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: apachebugs@perham.net


RPCProvider.java line 335 hardcodes a naming scheme for the response element of
operationName + "Response".  No problem in rpc since the Axis controls the
top-level element but it makes doc/lit unusable for those who write their own
WSDL and do not follow Axis conventions when creating their schema:

        /* Now put the result in the result SOAPEnvelope */
        /*************************************************/
        RPCElement resBody = new RPCElement(methodName + "Response");
        resBody.setPrefix(body.getPrefix());
        resBody.setNamespaceURI(body.getNamespaceURI());
        resBody.setEncodingStyle(msgContext.getEncodingStyle());