[
Lists Home |
Date Index |
Thread Index
]
Murali Mani wrote:
> I do not think Saxon is what I am looking for. What I want is I give a
> xpath expression/xquery etc, and some one gives it sax events. I want the
> query processor to operate on this stream of sax events from this point
> on, and give me values that satisfy the path expression/query.
So take a look at "Using XPath Expressions" chapter in Saxon
documentation at
http://saxon.sourceforge.net/saxon6.5.3/api-guide.html#Expressions
(or http://saxon.sourceforge.net/saxon7.8/api-guide.html#Expressions for
Saxon 7.X).
It sounds exactly what are you looking for.
> it says it can rebuild trees etc, which is not really possible in my
> scenario..
Well, rebuilding trees usually implies extensive querying, so usually
any XSLT processor exposes XPath API too.
> think of it more like your data is continuously streaming in,
> and is "infinitely" large..
Sounds like you don't want to build in-memory tree? Then XPath might be
not appropriate query language for you, because it operates on tree
level, hence allows reverse axes etc.
--
Oleg Tkachenko
http://www.tkachenko.com/blog
Multiconn Technologies, Israel
|
