Hi All, I would like to know if there's any plan for dom4j 2.0.0 to provide a pluggable XPath API instead to have a direct dependency on Jaxen library.
I like dom4j a lot ( i think it's the most useful xml api around ) and i want to use it. Despite this now i'm trying to use my code within eclipse and jaxen has a lot of problems with eclipse IP Policy restrictions. Dom4j itself has no problem, if you avoid to use the xpath functionality but, without xpath support it lost all the power. I like jaxen ( and i've no problem in using it ) but i could not use inside an eclipse project. I think that the best thing for dom4j project would be to have a pluggable API and let to choose at runtime level which xpath engine use. So within eclipse we can for example use the jdk provided XPath API and avoid problems. Any thoughts?? Andrea ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ dom4j-user mailing list dom4j-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dom4j-user
