Hi Hallvard.
That sounds interesting. You can call a function and navigate through its
results already. e.g.
document( 'foo.xml' )//bar[@x='123']/xyz
I'm just wondering why you think that a custom location step is requried.
e.g. your example could be reworked a little as follows...
James,
I'm just wondering why you think that a custom location step is requried.
e.g. your example could be reworked a little as follows...
ext:related-thing(thing)[@color='red']
When designing the XML structure you have to anticipate the navigation
pattern, to ensure that everything
Hmm,
Switching to preceding axis for clarity, but issue is the same.
From Michael Kay's XSLT Programmers Reference 2nd Edition by Wrox Press,
page 364:
preceding:
This selects all the nodes that appear before the origin node, excluding
the ancestors of the origin, in reverse document order. If
Actually, now that I re-read the spec, I'm not certain what my point was.
(One of those days).
Okay, an axis has a primary node type, but, so what?
Hmm...
Does
preceding-sibling::node()
manage to find the PI?
-bob
On Thu, 18 Apr 2002, Mattias Reichel wrote:
Hmm,
Hmmm... Sounds like a bug.
So, standard questions:
Which version of dom4j are you using?
James? Any thoughts?
-bob
On Thu, 18 Apr 2002, Mattias Reichel wrote:
Nope!
-Original Message-
From: bob mcwhirter [mailto:[EMAIL PROTECTED]]
Sent: den 18 april 2002 16:09
I use dom4j 1.3
-Original Message-
From: [EMAIL PROTECTED]
[mailto:jaxen-interest-
[EMAIL PROTECTED]] On Behalf Of bob mcwhirter
Sent: den 18 april 2002 16:18
To: Mattias Reichel
Cc: [EMAIL PROTECTED]
Subject: RE: [Jaxen] Possible bug with processing instructions
Hmmm...
