[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: sax parser and xpath

• To: "'Rasmussen, John'" <John.Rasmussen@F...>,"'bob mcwhirter'" <bob@w...>,<xml-dev@l...>
• Subject: RE: sax parser and xpath
• From: "Michael Kay" <michael.h.kay@n...>
• Date: Fri, 26 Jul 2002 16:27:10 +0100
• Importance: Normal
• In-reply-to: <91DF9655DE82164AA6EAA755DB6260A601B1B74E@M...>
• Reply-to: <michael.h.kay@n...>

> My process receives an xml doc, and uses a xpath expression 
> i.e. x/y/z[2] to designate a node on which to perform a 
> pagination operation.  I am proceeding with a jaxp sax class 
> that will walk through the doc and build the hierarchal node 
> name in order to test against the xpath expression.  

That's possible only for a very restricted subset of XPath (roughly the
subset used in XML Schema, for similar reasons). As soon as you get
something like

/x/y/z[t]

you're stuck: you can't test for that in a SAX application without
lookahead.

Michael Kay
Software AG
home: Michael.H.Kay@n...
work: Michael.Kay@s...  

• References:
  • RE: sax parser and xpath
    • From: "Rasmussen, John" <John.Rasmussen@F...>

• Prev by Date: Re: version numbers and infosets
• Next by Date: RE: version numbers and infosets
• Previous by thread: RE: sax parser and xpath
• Next by thread: Partitioning?
• Index(es):
  • Date
  • Thread