On Tue, 18 Sep 2001, Bryan Carpenter wrote:
> If I have a custom in-memory tree structure for which
> I'd like to provide read-only access through dom4j,
> what do I need to provide? From what I can see, I
> need to implement the Node interface for each node in
> my tree, but as I look at the Node interface, I see
> a lot of XPath functionality that could be significant
> work to implement beyond just the tree traversal and
> introspection functionality that my tree already
> has available. I was hoping to be able to put a thin
> layer over my tree and make it play in the dom4j
> world, but maybe that's unrealistic. Or, maybe I
> just haven't found the right info.
>
> Are there any helper classes for doing the XPath
> functionality, or perhaps a document that provides
> somewhat of a "cookbook" approach?
I'm not 100% certain I understand what you're trying to do, but with
regards to XPath stuff...
Using Jaxen (which the default dom4j implementations use under the covers,
actually), as long as you implement the dom4j interfaces, you get XPath
functionality "for free".
see:
http://jaxen.org/
or wait until James Strachan elaborates. James?
-bob
_______________________________________________
dom4j-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dom4j-user
