axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Daniels" <>
Subject Re: Compromise on streaming
Date Tue, 29 May 2001 04:40:43 GMT
Hi Simon!

Yep - so maybe change that to "the first Body element with no ID attribute".
Will that take care of it?  Is it possible to have a "main" body element
which itself has an ID?  Not using section-5 encoding, I don't think....


----- Original Message -----
From: "Simon Fell" <>
To: <>
Sent: Tuesday, May 29, 2001 12:15 AM
Subject: Re: Compromise on streaming

On Mon, 28 May 2001 23:45:58 -0400, in soap you wrote:

>4) If the service has NOT been determined by the time the SOAPSAXHandler
>arrives at the first <Body> element, it will attempt to set the service in
>the MessageContext based on the QName of that element.  This will result in
>calling the logic in (3) and therefore registering any service-specific

I've been working on my own streaming de-serializer model, so have
been keeping on eye on what you're upto :) apologies in advance if i'm
way off here, but doesn't this mean that this approach will fail to
deserialize this correctly ?

<s:Envelope ....>
<item id="ref-3">
<item id="ref-2">
<streetName>Spear Street</streetName>
<phoneNumber href="#ref-3"/>
<city>San Francisco</city>
<item id="ref-4">
<streetName>5th Ave</streetName>
<phoneNumber href="#ref-3" />
<city>New York</city>
<n1:addEntry id="ref-1" e:root="1">
<addresses xsi:type='e:Array' e:arrayType="n1:address[3]">
<address href="#ref-2"   />
<address href="#ref-4"   />
<address href="#ref-2"   />
<AddressToRegister>Simon Fell</AddressToRegister>


View raw message