Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: more XPath struggles (tDOM)

From: "Joseph J. Kesselman" <keshlam-nospam@-------.--->
To: NULL
Date: 5/2/2008 7:05:00 PM

Mikhail Teterin wrote:
> I got some progress... But the namespaces are defined in the document itself
> -- for example:
>  <xc:XmlCache xmlns:xc="XmlCache" xc:action="Update">
> why do I still need to specify them?

Because they could be set differently at different places in the 
document, and/or whatever generated your XPath might have different 
prefixes bound to those namespaces or vice versa. You need to provide a 
context so the system knows what you meant.

Some processors will let you specify a context node and will pick up the 
namespaces defined there. Again, check your docs.

 > It certainly works with xml_grep

I don't know xml_grep, so I can't advise. It may be assuming the root 
node as the context if not told otherwise. Or it may be flat-out broken 
and not processing namespaces correctly.

Say what you mean. The system can't read your mind, and shouldn't try.


transparent
Print
Mail
Digg
delicious
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent