Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 42394 invoked by uid 500); 14 May 2002 16:09:13 -0000 Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 42384 invoked from network); 14 May 2002 16:09:13 -0000 To: axis-dev@xml.apache.org Subject: Re: Purpose of SAX event recorders X-Mailer: Lotus Notes Release 5.0.5 September 22, 2000 Message-ID: From: "R J Scheuerle Jr" Date: Tue, 14 May 2002 11:09:12 -0500 X-MIMETrack: Serialize by Router on D04NM202/04/M/IBM(Release 5.0.9a |January 7, 2002) at 05/14/2002 12:09:13 PM, Serialize complete at 05/14/2002 12:09:13 PM MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_alternative 0058BB7086256BB9_=" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N This is a multipart message in MIME format. --=_alternative 0058BB7086256BB9_= Content-Type: text/plain; charset="us-ascii" But the multi-ref processing in encoding uses a fixups HashMap and other means to take care of this problem. I don't see any use of the SAX event recorders in the multi-ref processing. Rich Scheuerle XML & Web Services Development 512-838-5115 (IBM TL 678-5115) Sam Ruby/Raleigh/IBM@IBMUS 05/14/2002 09:24 AM Please respond to axis-dev To: axis-dev@xml.apache.org cc: Subject: Re: Purpose of SAX event recorders Glyn Normington wrote: > > Does anyone understand the purpose of using SAX event recorders in the Axis > deserialization components? > > I guess it's something to do with optimising serialization of the parse > tree, but it's not immediately obvious from the code :-). It would save me > some reverse-engineering effort if someone could describe the design in a > paragraph or two. I promise to put any succinct design principles in the > Architecture Guide for posterity. With multi-ref in SOAP, there are times when you encounter data that you don't know how to deserialize. As this data is coming in off a stream, there needs to be a place to "park" it until enough context is present. - Sam Ruby --=_alternative 0058BB7086256BB9_= Content-Type: text/html; charset="us-ascii"
But the multi-ref processing in encoding uses a fixups HashMap and other means to take care of this problem.
I don't see any use of the SAX event recorders in the multi-ref processing.


Rich Scheuerle
XML & Web Services Development
512-838-5115  (IBM TL 678-5115)


Sam Ruby/Raleigh/IBM@IBMUS

05/14/2002 09:24 AM
Please respond to axis-dev

       
        To:        axis-dev@xml.apache.org
        cc:        
        Subject:        Re: Purpose of SAX event recorders

       


Glyn Normington wrote:
>
> Does anyone understand the purpose of using SAX event recorders in the Axis
> deserialization components?
>
> I guess it's something to do with optimising serialization of the parse
> tree, but it's not immediately obvious from the code :-). It would save me
> some reverse-engineering effort if someone could describe the design in a
> paragraph or two. I promise to put any succinct design principles in the
> Architecture Guide for posterity.

With multi-ref in SOAP, there are times when you encounter data that you
don't know how to deserialize.  As this data is coming in off a stream,
there needs to be a place to "park" it until enough context is present.

- Sam Ruby

--=_alternative 0058BB7086256BB9_=--