axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tom Jordahl <>
Subject RE: Correctness of org.apache.axis.wsdl.toJava.Utils.getOperation QName
Date Thu, 03 Oct 2002 13:00:08 GMT


If I understand your question right, see section 3.5 of the WSDL 1.1 specification, the third
to last paragraph:
 "If use is encoded, then each message part references an abstract type using the type attribute."

WSDL spec should be at
Tom Jordahl
Macromedia Server Development

-----Original Message-----
From: Chris Burnley []
Sent: Wednesday, October 02, 2002 8:58 PM
Subject: Correctness of

I have a situation where I a client is using an element instead of a 
type for a message parameter in my WSDL file (simplified example 
attached). When I generate the stubs, the operation name call looks like 


rather than the expected:


I read the comments for getOperationQName and someone wrote:

       // NOTE: it is possible for someone to define a part as an element
       // while using rpc/encoded, which is wrong and we might want to 
catch it
       // here.

Is this actually true ? Could someone point me to the spec that points 
this out ? It seems that this could be easy to fix by adding

@@ -566,6 +566,9 @@
         if (ns == null) {
             ns = "";
+        else {
+            return new QName(ns, operationName);
+        }

to, revision RC1


Chris Burnley

View raw message