axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sam Carleton <scarle...@miltonstreet.com>
Subject Message coming back short
Date Tue, 29 Sep 2009 02:43:43 GMT
Silverlight 2.0 is calling an Axis2/C 1.6 server requesting a method that
takes a string as an in, though it isn't used and returns a complex result.
Here is the most relevant part of the WSDL:

      <xsd:element name="getDefaultSettings">
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="in" type="xsd:string"></xsd:element>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>

      <xsd:element name="getDefaultSettingsResponse">
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="defaultSettings"
type="tns:DefaultSettings"></xsd:element>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>

      <xsd:complexType name="DefaultSettings">
        <xsd:sequence>
          <xsd:element name="CompanyName" type="xsd:string"></xsd:element>
          <xsd:element name="EnableFavorites"
type="xsd:boolean"></xsd:element>
          <xsd:element name="EnableSlideShow"
type="xsd:boolean"></xsd:element>
          <xsd:element name="EventName" type="xsd:string"
nillable="true"></xsd:element>
          <xsd:element name="PhoneNumberFormat"
type="xsd:string"></xsd:element>
          <xsd:element name="Theme" type="xsd:string"></xsd:element>
          <xsd:element name="ThumbnailSize" type="xsd:int"></xsd:element>
          <xsd:element name="TimeoutAfter" type="xsd:int"></xsd:element>
          <xsd:element name="TimeoutStarts" type="xsd:int"></xsd:element>
          <xsd:element name="UserLang" type="xsd:string"></xsd:element>
        </xsd:sequence>
      </xsd:complexType>

Thanks to TCPMon, the request Envelope is this:

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
   <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="
http://www.w3.org/2001/XMLSchema">
      <getDefaultSettings xmlns="urn:mmpp:parataMgr">
         <in xmlns="">not used</in>
      </getDefaultSettings>
   </s:Body></s:Envelope>

The response is:

   <soapenv:Envelope xmlns:soapenv="
http://schemas.xmlsoap.org/soap/envelope/">
      <soapenv:Body>
         <n:getDefaultSettingsResponse xmlns:n="urn:mmpp:parataMgr">
            <defaultSettings>
               <CompanyName>Miltonstreet Photography</CompanyName>
               <EnableFavorites>true</EnableFavorites>
               <EnableSlideShow>true</EnableSlideShow>
               <EventName>BigEvent</EventName>
               <PhoneNumberFormat>True</PhoneNumberFormat>
               <Theme>Blue</Theme>
            </defaultSettings>
         </n:getDefaultSettingsResponse>
      </soapenv:Body>
   </soapenv:Envelope>

A number of the elements in the defaultSettings are simply missing.  All the
elements where not in order originally, so I sorted the WSDL, regenerated
the source and recompiled and the same elements are always missing.  Any
thoughts on what is going on?

Sam

Mime
View raw message