axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 26640] New: - In sample clients, call to org.apache.axis.client.Call's setOperationName use wrong namespace
Date Tue, 03 Feb 2004 18:00:35 GMT
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=26640>.
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=26640

In sample clients, call to org.apache.axis.client.Call's setOperationName use wrong namespace

           Summary: In sample clients, call to org.apache.axis.client.Call's
                    setOperationName use wrong namespace
           Product: Axis
           Version: 1.2 Alpha
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Samples
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: jdibble@amberpoint.com


In the sample client applications in the samples/userguide directory, the call 
to the org.apache.axis.client.Call class's setOperationName method uses an 
incorrect namespace to qualify the operation name.

For example, Client.java in example3 uses the service name ("MyService") to 
qualify the operation name.  According to the WSDL file of the deployed web 
service, the operation should be qualified by the 
namespace "http://example3.userguide.samples".  Because Axis is lenient around 
the qualified namespace for an operation, this does not affect the workings of 
the sample application.  However, other products used in conjunction with Axis 
follow the WSDL specification most closely, and therefore do not recognize the 
operation because it is qualified by the wrong namespace.

Mime
View raw message