Hi PJ > When using the ElementHandler feature of the SAXReader, there is only a > subset of XPath available (eg no element predicates can be used). Is there > any documentation on what can and can't be used?
It only supports simple, element name based addressing right now like /foo/bar > I think it would be useful if this feature was available via the > SAXContentHandler also. Yes, Laurent Caillette and myself have been exchanging some ideas and emails lately, we hope to get a full implementation of XPath based pattern notification working really soon now, its probably a week or two away. So you'll soon be able to do more complex notifications based on XPaths such as a//b[@x='12]/c > In my application, I have a SAX event stream and want to build a Document > without having to reparse it. > I suppose it would be possible for me to write a dummy implementation of > XMLReader which just passed my SAX event stream to the SAXReader directly. You mean you want to pass SAX events straight into SAXReader without reparsing it? Sounds a good idea to me. The SAXContentHandler implements the SAX interfaces, ContentHandler, LexicalHandler and so on, so you could just use that class explicitly. Do let us know if there's anything we can do to make SAXContentHandler easier to use stand-alone. James _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ dom4j-dev mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dom4j-dev
