> I didn't think it was valid to use a wildcard for a namespace prefix. If
> thats the case then above would have to be done as
Well, re-reading the specs, I'm not sure whether it's valid or not. I'm not
interrested in using such a syntax, I was just looking for the strange
behaviour I've already mentioned.
In order for everyone to see what's going wrong (me or Jaxen ;-) ), the
simple program attached gives the following results here :
D:\Work\jaxenbug>javac -classpath .;jaxen-full.jar;saxpath.jar;xerces.jar
DOMDem
o.java
D:\Work\jaxenbug>java -classpath .;jaxen-full.jar;saxpath.jar;xerces.jar
DOMDemo
++++++++++++++++++++++++++++++++++
XPah:h piz:pizza(/child::piz:type)
Document :: pipo.xforms
Context :: xform:instance
XPath :: piz:pizza/piz:type
Results
----------------------------------
null
++++++++++++++++++++++++++++++++++
XPah:h child::*:pizza/child::*:type
Document :: pipo.xforms
Context :: xform:instance
XPath :: *:pizza/*:type
Results
----------------------------------
[piz:type: null]
++++++++++++++++++++++++++++++++++
XPah:h self::node()/child::piz:pizza/child::piz:type
Document :: pipo.xforms
Context :: xform:instance
XPath :: ./piz:pizza/piz:type
Results
----------------------------------
[piz:type: null]
To sum up,"*:pizza/*:type" and "./piz:pizza/piz:type" gave expected results
(well, according to me of course), whereas "piz:pizza/piz:type" found null
(not nothing, really a null pointer !!).
The sad thing being that I must use the latter syntax :'-(.
Jérôme
pipo.xforms
DOMDemo.java
