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 12758] - Deserialization of complex classes throws SAXException
Date Fri, 27 Sep 2002 15:06:58 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=12758>.
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=12758

Deserialization of complex classes throws SAXException

butek@us.ibm.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|1.0 Final                   |post-1.0



------- Additional Comments From butek@us.ibm.com  2002-09-27 15:06 -------
This is a different problem, and possibly not AXIS's, so I'm downgrading the 
target to post-1.0.  The response message seems to be bad.

HTTP/1.1 200 OK
Server: Microsoft-IIS/5.0
Date: Fri, 27 Sep 2002 14:30:14 GMT
Content-Type: text/xml
Content-Length: 2092
Content:

<?xml version="1.0"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">
  <SOAP-ENV:Body 
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <NS1:getHireFromCustomerLicenceResponse xmlns:NS1="urn:THireIntf-IHire" 
xmlns:NS2="urn:uHireInfo" xmlns:NS3="urn:uHireItemInfo">
      <return href="#1"/>
      <NS2:THireInfo id="1" xsi:type="NS2:THireInfo">
        <Number xsi:type="xsd:int">335</Number>
        <SourceDepot xsi:type="xsd:string">TWEED</SourceDepot>
        <DestinationDepot xsi:type="xsd:string">TWEED</DestinationDepot>
        <StartTime xsi:type="xsd:dateTime">2002-09-24T16:34:30.000</StartTime>
        <FinishTime xsi:type="xsd:dateTime">2002-09-24T20:34:30.000</FinishTime>
        <TimeLength xsi:type="xsd:int">4</TimeLength>
        <TrailerTypeCode xsi:type="xsd:string">HORSE</TrailerTypeCode>
        <TrailerCode xsi:type="xsd:string">902</TrailerCode>
        <ApplySackTruck xsi:type="xsd:boolean">false</ApplySackTruck>
        <SackTruckCode xsi:type="xsd:string"></SackTruckCode>
        <ApplyContentsInsurance 
xsi:type="xsd:boolean">false</ApplyContentsInsurance>
        <LeavingMetro xsi:type="xsd:boolean">false</LeavingMetro>
        <Returned xsi:type="xsd:boolean">true</Returned>
        <ReturnedTime 
xsi:type="xsd:dateTime">2002-09-27T16:04:42.000</ReturnedTime>
        <CustomerNumber xsi:type="xsd:int">76</CustomerNumber>
        <TotalPrice xsi:type="xsd:double">-2</TotalPrice>
        <HireItems xsi:type="SOAP-ENC:Array" 
SOAP-ENC:arrayType="NS3:THireItemInfo[2]">
          <item href="#2"/>
          <item href="#3"/>
        </HireItems>
      </NS2:THireInfo>
      <NS3:THireItemInfo id="2" xsi:type="NS3:THireItemInfo">
        <Item xsi:type="xsd:string">LF</Item>
        <Name xsi:type="xsd:string">Late Fee</Name>
        <Price xsi:type="xsd:double">48</Price>
      </NS3:THireItemInfo>
      <NS3:THireItemInfo id="3" xsi:type="NS3:THireItemInfo">
        <Item xsi:type="xsd:string">RTD</Item>
        <Name xsi:type="xsd:string">Returned Trailer Deposit</Name>
        <Price xsi:type="xsd:double">-50</Price>
      </NS3:THireItemInfo>
    </NS1:getHireFromCustomerLicenceResponse>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Note that there are hrefs in the message.  And note further that the 
multi-ref items that the hrefs are pointing to are INSIDE the 
"getHireFromCustomerLicenceResponse" response clause.  The response scope should 
contain one entry per parameter.  It SHOULD NOT contain the multi-ref'ed items.  
Those belong in the scope of the SOAP body.

At least this is the interpretation of AXIS.  If you could prove us wrong, then 
of course we'll patch it, but we believe AXIS is doing the right thing.

Is there a way to turn off multiref messages on your server?  If you can do that 
(you don't NEED multirefs in this example, at least) then that might be a good 
workaround for you.

Mime
View raw message