I haven't been able to figure out a way to "plug in" Saxon so that it can be used via the org.jdom.xpath.XPath class in the JDOM system. I know that JDOM documents can be used in Saxon via the net.sf.saxon.jdom package, but it would be nice to be able to stay within one consistent system. If anybody can comment on a way to do this, or why it's not easily possible, I would appreciate it.
It would be nice (and perhaps it exists but I'm missing it) if Saxon itself incorporated a standard set of methods for manipulating XML documents that integrated with its own tree structures - something fully general purpose that permits efficient arbitrary construction/addition/removal/navigation of XML tree nodes. The JDOM api itself, with its unrestrictive license, seems a good candidate.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.