Strange behavior on soap message generated by axis1.1?

[Liu, Scott]

I used Axis 1.1 RC2 before I switched to the stable Axis 1.1 final version (June 2003). Then the RESPONSE soap message in my service was changed to an undesired form. The message looks like this.   <?xml version="1.0" encoding="UTF-8"?>       <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">          <soapenv:Body>              <addResponse xmlns="urn:messages.webservices">                <AddResponse xmlns="urn:messages.webservices">                     ç======================= This is extra                   <status isSuccess="true"/>                   <ns1:recordRef key="89" type="case" xmlns:ns1="urn:dto.webservices"/>                </AddResponse>                                                                         ç======================= This is extra             </addResponse>          </soapenv:Body>       </soapenv:Envelope>     The response was defined as the follows.               <message name="addResponse">                         <part name="parameters" element="types:addResponse"/>             </message>             <!-- Add -->             <complexType name="AddResponse">             <sequence>                 <element ref="msg:status"/>                 <element ref="dto:recordRef" minOccurs="0"/>             </sequence>             </complexType>             <element name="addResponse" type="msg:AddResponse"/>   Why did it include the complex type “AddResponse” in the soap message?   If I switch to the old version it would be fine.   Can someone point me to the solution or the axis class which maybe responsible for the behavior?   Thanks a bunch,   Scott