> I just wondered if we need both JaXPath and BaseXPath in org.jaxen package.
> Maybe we could just have one implementation, say BaseXPath and one interface
> that all XPath implementations implement?
I forget why, but I think the split made testing easier. I might've
just been muddled too. If you can find no reason for the two, then
getting rid of one or the other is fine by me.
> Another thought; how about a generic XPath implementation. Say
>
> org.jaxen.generic.XPath
>
> Which depending on the type of the context it could deduce if it was DOM,
> dom4j, EXML or JDOM and call the necessary exact XPath implementation?
> Hopefully it could share the XPath expression though.
Yah, XPath expressions are shareable, no problem. You just need some
logic to determine which Navigator to pass to the forms of
selectNodes(...) et al that take a Navigator.
-bob
_______________________________________________
Jaxen-interest mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jaxen-interest
