On Wed, 12 Sep 2001, Jérôme Nègre wrote:
> > 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 :
>
This is the result I get with the current cvs version of Jaxen:
++++++++++++++++++++++++++++++++++
XPah:h child::piz:pizza/child::piz:type
Document :: pipo.xforms
Context :: xform:instance
XPath :: piz:pizza/piz:type
Results
----------------------------------
[piz:type: 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]
Interestingly, it wouldn't run at first because Xerces didn't recognize
the load-external-dtd option that DOMDemo specifies. In your case,
piz:pizza/piz:type was incorrectly interpreted as piz:pizza(/piz:type).
It'd seem to me that you have a version problem; you're using a different
version of xerces, and probably also a different version of SaxPath, than
the one currently used by Jaxen.
- Erwin
_______________________________________________
Jaxen-interest mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jaxen-interest
