I'm having a problem
with the following type of _expression_ in Jaxen:
document("../data/someFile.xml")/a/b/c AND /x/y/z
I've stepped through
the code, and into the Jaxen code, and it seems that the _expression_ following
the AND is being evaluated against the context supplied by the document
function. We thought that the /a/b/c would be evaluated against the
document stored on disk, and the /x/y/z against the current document we are
running the xpath against.
We are using dom4j,
so the _expression_ is being evaluated like this:
Object selectedNode = doc.selectObject(expr);
where expr
is the string containing the xpath.
If we break the
_expression_ into just the LHS and RHS, each evaluates true standing alone.
But when combined with the AND, the LHS evals true and the RHS evals
false. I noticed in the _expression_ when stepping through Jaxen that the
RHS context references the document returned from the document() function in the
LHS. This is not what I expected.
Are we doing
something wrong here, or is this a Jaxen bug????
Thanks...
-David
Hooker-
-Sr. Architect,
Platform-
