On Fri, 17 May 2002, James Strachan wrote:
> This is an XPath 1.0 thing - its nothing Jaxen specific. In XPath the
> expression
>
> /foo/bar
>
> means foo and bar are not in any namespace. Binding non-prefixes to some
> namespace is an error.
are you saying that Jaxen resolves a QName without prefix to the default
(null prefix) namespace URI in regards to function names? otherwise why
would it fail?
my interpretation of the spec is that unless the function QName has a
prefix, no namespace prefix is resolved at all - the URI is always null,
regardless of the default namespace of the input document.
/m
_______________________________________________________________
Hundreds of nodes, one monster rendering program.
Now that's a super model! Visit http://clustering.foundries.sf.net/
_______________________________________________
Jaxen-interest mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jaxen-interest
