This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Feeding DOMs to XSLT Processors
- To: jonsmirl at mediaone dot net, xsl-list at mulberrytech dot com
- Subject: Re: Feeding DOMs to XSLT Processors
- From: Michael Harry Scepaniak <ihispanic at yahoo dot com>
- Date: Mon, 7 Feb 2000 06:50:45 -0800 (PST)
- Reply-To: xsl-list at mulberrytech dot com
Jon,
Both Michael Kay and yourself recommended this approach (transform the
incoming data into SAX Events instead of DOM). I was hoping you could
give me your input on the situation described below.
We're getting data from the mainframe in the form of a big, long
string. The field offsets are determined by a COBOL copybook. We
pre-process the copybook into a DOM. At runtime, we use the copybook
DOM to parse the mainframe data string into another DOM and then pass
this DOM to the XSLT processor.
Would the following be feasible -- Pre-process the copybook into a SAX
InputSource instead of a DOM, at runtime, use the copybook SAX events
to parse the mainframe data string into a separate set of SAX events,
and then pass these events to the XSLT processor?
I don't have much knowledge regarding SAX and am simply looking for a
high level "yes" or "no", but would welcome any further explanation.
Thanks.
Mike...
> Date: Thu, 3 Feb 2000 13:57:14 -0500
> From: "Jon Smirl" <jonsmirl@mediaone.net>
> Subject: Re: Feeding DOMs to XSLT Processors
>
> I have found it more efficient to transform the incoming data into
SAX
> Events instead of DOM. The SAX events approach works with all of the
> XSL
> implementation.
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list