This usually means there's an XML namespace at work. Take a close look
at that 'foo' element, and see if it has a namespace associated with it.
If my guess is right, then you might find various past conversations
about namespaces interesting, too.
http://marklogic.markmail.org/search/?q=namespace
-- Mike
On 2009-07-17 15:02, Charles Blair wrote:
I'm having the same problem with either of the above functions. I'm
using them to get a response from a remote server. The server is
returning XML, but because of the content-type header the return value
is coming back as binary. I'm treating this as XML via the format as
xml option, as documented. xdmp:describe says that the relevant part
of the return value (i.e., not the remote server's response) is a
document, and that's the part I'm dealing with.
However, XPATH expressions that name elements don't work on that part
of the return value for these functions. For example, I can't get at
element foo directly; I have to use positional notation, such as
$document/child::node()[1]/child::node(). So, what is the problem
here, and what (if anything) is the solution?
Thanks.
_______________________________________________
General mailing list
[email protected]
http://xqzone.com/mailman/listinfo/general
_______________________________________________
General mailing list
[email protected]
http://xqzone.com/mailman/listinfo/general
