So , if we have already bought Saxon 9ee , We might as well use Saxon API
for executing xpaths from within java.
I will also consider trying out xom or jdom2 ...If there are any good
buying points over Saxon.
On Feb 9, 2016 6:50 AM, "Michael Kay mike(_at_)saxonica(_dot_)com" <
xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com> wrote:
So the xpath library within Saxon API uses jdom2 / xom?
Is it a right inference ?
Saxon has its own internal tree model, called the TinyTree, which is
optimized for XSLT and XPath processing. It's immutable and very compact,
and has very fast name matching. It's not intended for direct use by
ordinary Java applications.
Saxon also supports XSLT/XPath/XQuery processing against DOM, JDOM, JDOM2,
DOM4J, XOM, or AXIOM trees. There's a considerable performance penalty over
Saxon's internal tree model, but if you want to access the tree from Java
as well as via XPath (especially update access), this is the way to go.
Michael Kay
Saxonica
XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
EasyUnsubscribe <-list/1311928> (by
email <>)
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--