OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: General SAX2 Observations

[ Lists Home | Date Index | Thread Index ]
  • From: David Megginson <david@megginson.com>
  • To: xml-dev@XML.ORG
  • Date: Wed, 15 Mar 2000 06:58:10 -0500 (EST)

Jon Smirl writes:

 > But what if you don't know the stylesheet ahead of time and it's name is
 > being computed dynamically?
 > 1) create the XML parser
 > 2) call parse()
 > 3) catch the pi event and get the name of the stylesheet
 > 4) Create the XSLProcessor object
 > 5) call parse() on the XSLProcessor
 > 6) get the document handler from XSLProcessor
 > 7) set the parser's document handler to be the XSLProcessor
 > 8) But now you're stuck, if you return out of parse() the XSLProcessor will
 > terminate and not see the SAX events from the parser

I think that this is just a specific example of the recursive
processing problem.  When you find the stylesheet PI, you should
allocate a *new* parser object, process the stylesheet with it, then
continue with regular SAX processing in the original parser (in SAX2,
"Parser" becomes "XMLReader") which will not have lost track of your
original state.

All the best,


David Megginson                 david@megginson.com

This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS