Hello Fellow Muse Users,

 

I've noticed that Muse's WSDL-to-Java tools don't seem to handle complex
return types in a particularly elegant way.  For example, if I define
the following type...:

 

  <wsdl:types>

    <xsd:schema elementFormDefault="qualified"
targetNamespace="http://ws.disco.xerox.com/MyService";>

 

      <xsd:element name="MyMethodResponse">

        <xsd:complexType>

          <xsd:sequence>

            <xsd:element name="foo" type="xsd:string" maxOccurs="1"
minOccurs="1"/>

            <xsd:element name="bar" type="xsd:int" maxOccurs="1"
minOccurs="1"/>

          </xsd:sequence>

        </xsd:complexType>

      </xsd:element>

            

    </xsd:schema>

  </wsdl:types>

 

And then define a message as such:

 

  <wsdl:message name="MyMethodOutputMessage">

    <wsdl:part name="result" element="tns:MyMethodResponse"/>

  </wsdl:message>

 

Muse then generates a method that looks something like this:

 

public org.w3c.dom.Element myMethod() throws Exception;

 

I would have expected (hoped?) it to create a Java (bean-like, maybe)
object that mapped to my type definition.  Something like:

 

public class MyMethodResponse {

  String foo;

  int bar;

}

 

Is it the case that Muse will always convert complex return types to
this generic Element interface?

 

Thanks,

Bob

Reply via email to