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/07/11 08:14:26 UTC

DO NOT REPLY [Bug 21488] New: - message style method signatures unclear

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

message style method signatures unclear

           Summary: message style method signatures unclear
           Product: Axis
           Version: 1.1
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Documentation
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: wbredenkamp@pnp.co.za


I think I may have found a bug in org.apache.axis.description.ServiceDesc.
In
        private int checkMessageMethod(Method method)
you do the following:
        if ((params[0] == SOAPEnvelope.class) &&
            (params[1] == SOAPEnvelope.class) &&
            (method.getReturnType() == void.class)) {
            return OperationDesc.MSG_METHOD_SOAPENVELOPE;
        }

This checks the method signature against org.apache.axis.message.SOAPEnvelope.
Should it not be checked against javax.xml.soap.SOAPEnvelope instead (as a 
matter of JAXM compliancy)?

If not, please clarify the user guide documentation which describes the 
signatures that are acceptable for message style service methods.

thank you
Werner Bredenkamp
Cape Town
South Africa