Hi Jos, thanks for your reply, the XPath expression is already known before parsing the document since the XInclude processor catches the xpointer reference before including the document. I think your solution works but I've the suspect just for a limited subset of the XPath expressions, the exception comes when an expression contains siblings/parent references... What do you think about it? Best regards and thanks for your hint! Simone
On Mon, Nov 23, 2009 at 7:12 AM, Jos Snellings <[email protected]> wrote: > Hmmm, I guess the XPath expression is known before the parsing begins? > I remember I have done a similar thing, where a chunk had to be isolated > from a document that came by via a SAX stream, but here the xpath > expression was something like: "/element1/elemen...@id=somenumber]". > > Theorem: any XPath expression can be evaluated with a SAX filter. > Proof? > Do you know some exceptions? > > Jos > > -- http://www.google.com/profiles/simone.tripodi
