Lists Home |
Date Index |
| There are two Java implementations that I know of, that provide some kind of
| reasonable interface for querying a DOM tree using XPath in a standalone
| application (Xalan and Jaxen), and only Jaxen provides a full, useable
Oracle's XML Parser also provides an XPath engine that's
woven into our DOM implementation. Using it is as easy as:
We find most of our Oracle XDK customers avoid DOM programming
and just use these three methods to work with their documents
due to their greatly improved ease of use. Our users haven't
asked for any more functionality than what they can get
with these three simple methods. Each one also has an overloading
that takes an NSResolver interface if your XPath pattern includes
qualified names that need to be resolved.
Oracle XDK for Java is fast, free, supported, and downloadable at:
Steve Muench - Developer, Product Manager, XML Evangelist, Author
"Simplifying J2EE and EJB Development with BC4J"
"Building Oracle XML Applications" - www.oreilly.com/catalog/orxmlapp
| I have to say, most XPath engines are horribly badly engineered for
| standalone applications. Even Xalan makes it a nightmare to bind
| user-defined variables for a query. The Xalan2 api docs state that
| variable binding has been made "more low-level" still.. why??
| I won't even start with my success of binding my own variables in the
| .NET System.Xml classes. Their System.Xml.XPath classes do not even
| envisage that someone might ever want to do this.. you have to pick out
| Xsl classes, and then the exceptions start...
| A couple of use cases for the XPath specifications could have prevented
| this mess.
| The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
| initiative of OASIS <http://www.oasis-open.org>
| The list archives are at http://lists.xml.org/archives/xml-dev/
| To subscribe or unsubscribe from this list use the subscription
| manager: <http://lists.xml.org/ob/adm.pl>