So if such an optimization was added there would be a way to by-pass it
as well? [This can't just be if Xalan is not present -- as Xalan is
present for other reasons.]
--
Jess Holle
Dmitri Plotnikov wrote:
Jess,
JXPath has always supported Xalan through JAXP DOM APIs. What you may have
seen
Dmitri Plotnikov wrote:
Jess,
JXPath has always supported Xalan through JAXP DOM APIs. What you may have
seen in the source code of JXPath is some attempts to optimize JXPath when it
is used specifically in combination with Xalan. You would not be interested in
that optimization, because it
Jess,
First of all, this discussion is probably better suited to the commons-user
mailing list.
As far as your specific questions are concerned, getValue() will always return
a primitive value (Number, Boolean or String) when applied to DOM.
selectSingleNode() will return either a
P.S. Also, I must admit this message is somewhat of a test. If no one
responds, then I can assume the JXPath community is not active enough to
be worth considering over sticking with an old version of Xalan for the
forseeable future.
Jess Holle wrote:
I am using Xalan 2.1.0 for XPath
Jess,
JXPath has always supported Xalan through JAXP DOM APIs. What you may have
seen in the source code of JXPath is some attempts to optimize JXPath when it
is used specifically in combination with Xalan. You would not be interested in
that optimization, because it would only be applied
Jess,
Sorry, I misspoke. Of course, what I wanted to say was that JXPath has always
supported Xerces, which is the XML parser bundled with Xalan. Thus, it can
work side-by-side with Xalan.
- Dmitri
Dmitri Plotnikov [EMAIL PROTECTED] wrote:
Jess,
JXPath has always supported Xalan through
Hi,
I am also looking at the same optimization, but not in a way that Xalan handles
the xpath,
but in such a way that a metamodel (DOM or your own) can optimize the query
implementation
itself.
I was thinking of having a nodepointer recognizing the model, and having the
option to
pass the
