That would not be XPath, but a small subset of XPath. What parts of XPath are you planning to support?
Andreas On Tue, Apr 2, 2013 at 8:49 AM, Isuru Ranawaka <[email protected]> wrote: > hi Andreas , > > Current Implementation of Streaming Xpath Parser is not support for Xpath > expressions that having predicates. On the Other hand it Operates on top of > the OMElement .What I suggest is rewrite Xpath Parser for evaluate Xpath > Expressions on top Of the XMLStream.That means with out building OMElement > or any Other Object Model getting XML Events From XMLStream and Evaluate > Xpath. For that Xpath Compiler should have to be designed and Need to figure > out Object Model for represent Xpath Expression .By Using that Xpath Model > and XMLStream it should be able to evaluate Xpath. > > > On Tue, Apr 2, 2013 at 12:44 AM, Andreas Veithen <[email protected]> > wrote: >> >> On Sun, Mar 24, 2013 at 9:19 AM, Isuru Ranawaka <[email protected]> >> wrote: >> > 1. ) Streaming Xpath Parser is developed for a ESB which get AXIOM >> > Object >> > and traverse through it and get results.here the main concern is to >> > improve >> > the performance of xpath parsing by specifying specific rules relevant >> > to >> > the domain. (e.g if there is expression such as “/data/book” it only >> > give >> > the first child element under the data element ) what i suggest is >> > creating >> > a XpathEngine which does not consume any external object model and it >> > will >> > operate on top of the XML Stream that means traverse xmlstream and >> > evaluate >> > xpath. >> >> Can you explain how this would work for an expression like >> /data/book[isbn='1-84356-028-3']? >> >> Andreas >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
