If you use something like this:
xindice xpath -c /db/junk -s "glop=http://blah"; -q "//glop:zork"
the result is unambiguous:
http://blah"; xmlns:src="http://xml.apache.org/xindice/Query";
src:col="/db/xones/tupletest" src:key="nstest"
xmlns:glop="http://blah";>abc
And
http://xml.apache.org
--- Jeff Greif <[EMAIL PROTECTED]> wrote:
> Vanessa and Xindice developers,
> In the prior version (dbxml-1.0b4), using this
> document in the collection
> /db/junk,
>
>
> owner="/sysinfo/Webalo/users/sysroot"
> xmlns:glop="http://blah";>
>glop:urk="/rootview~!~">
> /rootvie
Mark J. Stang wrote:
> Don't need no stinkin namespaces ;-). I try to be as vanilla
> as possible. No namespaces, DTDs or anything out of the
> ordinary.
Hmmm...an interesting form of purism :) However, in real-life namespaces are
essential and therefore quite ordinary.
I've figured out m
Don't need no stinkin namespaces ;-). I try to be as vanilla
as possible. No namespaces, DTDs or anything out of the
ordinary.
Vanessa Williams wrote:
> Thanks for the idea, Roman. I tried it, but unfortunately, it doesn't work.
> :-(
>
> I did manage to discover that XPath itself does not su
Vanessa and Xindice developers,
In the prior version (dbxml-1.0b4), using this document in the collection
/db/junk,
http://blah";>
/rootview
xyz
the following queries worked as expected
dbxml xpath -c /db/junk -q "//glop:zork"
dbxml xpath -c /db/junk -q "//[EMAIL PROTECTED]:u
Thanks for the idea, Roman. I tried it, but unfortunately, it doesn't work.
:-(
I did manage to discover that XPath itself does not support namespaces in
any way. It uses only the prefixes and depends on "the system" (for
instance, an XSLT stylesheet processor) to define a context (i.e. To map
tho
Vanessa Williams wrote:
I'm still struggling with exceptions being thrown related to namespaces, but
I've narrowed down the problem.
It's even worse than it appears. I've recently discovered this: suppose
you have a collection /db/nstest, containing two documents:
/db/nstest/a:
Hi Vanessa,
Perhaps it is possible to use notation as for indexing (see
http://localhost:4080/AdministratorsGuide.html#N46):
". . .
Note: In order to index a namespace other than the default namespace, you must
prepend your pattern components with a URI placed in square brackets. Example:
[http:
I'm still struggling with exceptions being thrown related to namespaces, but
I've narrowed down the problem.
Take this example document:
http://www.somedomain.com/someschema.xsd";>
http://www/somedomain.com/someschema2.xsd";>
The document is well-formed and valid and is added to a Xind
