There seems to be a bug in SimpleNamespaceContext.addElementNamespaces which copies
the default namespace over and screws up the function context, in that it will
suddenly use the default namespace to try and resolve functions, whereas it should use
no namespace.
>>> "Paul Brown" <[EMAIL PROTECTED]> 10/13/02 02:48am >>>
This ought to be a FAQ somewhere... The namespace prefix that is in the source
document is a red herring. In XPath, the unnamespace is always represented by a
non-prefixed path. For a non-trivial default namespace, you just need to map a prefix
to it.
So, in
<foo xmlns="bar">
If you have
fneh --> bar
you would be able to use
fneh:foo
to describe the step.
-- Paul
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Jaxen-interest mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jaxen-interest
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Jaxen-interest mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jaxen-interest
