JPath is now in the sandbox. It is a contribution by PLOTNIX, INC
For your convenience I put the API docs on the PLOTNIX' website:
http://www.plotnix.com/jpath/api/
There are some differences between JPath and the original JXPath projects:
1. JPath supports variables: "$books[$index]/title". You can use the default
pool of variables or supply your own. For example, if JPath is used by a
servlet, a custom implementation of the Variables interface could work with
HTTP Request or Servlet Context or both. You can even change variables
using calls like context.setValue("$index", new Integer(2)).
2. JPath supports not only regular JavaBeans, but also objects with dynamic
properties. Out of the box it works with Maps. You can make it work with
other types of name/value mappers, like HTTP Request. Simply implement the
DynamicPropertyHandler interface and register it with JPathIntrospector.
3. The JPath APIs have been refactored to allow for transparent replacement
of implementations using different XPath interpretation techniques. JPath
automatically chooses an implementation by utilizing a mechanism similar to
the one used by JAXP, JNDI etc. The current default implementation of JPath
depends on Xalan. It creates a light-weight DOM tree and then passes that
tree to the Xalan XPath interpreter. When we are done with the
implementation of JPath that does not build a tree, but instead accesses
JavaBeans directly - we will substitute it transparently.
Please, check JPath out and provide your feedback.
- Dmitri Plotnikov
[EMAIL PROTECTED]
