blocks|key|975307|text|您很可能需要在xpath库中注册该名称空间uri。根据库的不同，您可能会使用“default”前缀，也可能需要为其指定一个命名前缀并在xpath查询中使用它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|975308|例如，在php中(因为你没有指定语言)，使用DOMXPath你可以这样做：|975309|$xpath+=+new+DOMXPath($document);
$xpath->registerNamespace('x',+'http://schemas.microsoft.com/sharepoint/soap/');
$xpath->query('/x:List/x:Fields/x:Field');|code-block|syntax|javascript|975310|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

You most likely have to register that namespace uri with your xpath library. Depending on the library, you may be able to use the 'default' prefix or you may need to give it a named prefix and use that in your xpath queries.

For example, in php (since you didn't specify a language) using DOMXPath you could do something like this:

<pre><code>$xpath = new DOMXPath($document);
$xpath-&gt;registerNamespace('x', 'http://schemas.microsoft.com/sharepoint/soap/');
$xpath-&gt;query('/x:List/x:Fields/x:Field');
</code></pre>

blocks|key|975362|text|List元素定义了一个默认的名称空间，内部的所有元素都采用这个名称空间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|975363|因此，您需要忽略元素名称空间，如下所示：|975364|/*[local-name()='List']/*[local-name()='Fields]/*[local-name()='Field]|code-block|syntax|javascript|975365|但这意味着xpath将使用List+-+Fields+-+Field拾取任何其他元素|975366|您可以执行名称空间检查以及本地名称检查，如下所示：|975367|/*[local-name()='List'+and+namespace-uri()='http://schemas.microsoft.com/sharepoint/soap/']/*[local-name()='Fields'+and+namespace-uri()='http://schemas.microsoft.com/sharepoint/soap/']/*[local-name()='Field'+and+namespace-uri()='http://schemas.microsoft.com/sharepoint/soap/']|975368|或者，您可以在库中注册名称空间，然后显式指定该名称空间的前缀，并将其添加到xpath表达式中，xpath表达式的方法取决于您正在使用的库。|975369|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|V|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|X|8|@]|9|@]|A|$G|H]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

The List element has been defined with a default namespace and this is adopted by all elements inside.

You therefore need to ignore the element namespace like so:

<pre><code>/*[local-name()='List']/*[local-name()='Fields]/*[local-name()='Field]
</code></pre>

but this means that the xpath will pick up any other element with List - Fields - Field 

You can do a namespace check as well as a local-name check like so:

<pre><code>/*[local-name()='List' and namespace-uri()='http://schemas.microsoft.com/sharepoint/soap/']/*[local-name()='Fields' and namespace-uri()='http://schemas.microsoft.com/sharepoint/soap/']/*[local-name()='Field' and namespace-uri()='http://schemas.microsoft.com/sharepoint/soap/']
</code></pre>

Or you can register the namespace with the library and then explicitly specify the prefix for that namespace and add it to xpath expression, the method of which is dependent on the library you are using.

blocks|key|975421|text|我在使用Xalan-c时遇到了这个问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|975422|我最初没有完全理解的一点是，XPath或XSLT名称空间别名/前缀可以与文档的名称空间别名/前缀不同-这取决于您的名称空间解析器。|975423|看起来，如果文档上有名称空间，则除非使用名称空间，否则它无法与路径元素匹配。(标准但不总是遵循？)|975424|XalanDocumentPrefixResolver会将XPath或XSLT名称空间映射到URI，并尝试通过获取前缀来为它们提供id+-如果没有前缀，则使用转换为xmlns的名称|975425|/xmlns:List/xmlns:Fields/xmlns:Field|offset|length|style|CODE|975426|或者，您也可以创建自己的解析器，但它仍然需要在xpath中使用的最小名称空间:(|975427|这是我在测试时一起破解的一个，不能保证内存|975428|//+don't+care+what+prefix+given,+there+can+only+be+the+one
struct+NoPrefixResolver+:+public+xalanc::PrefixResolver+{

++++NoPrefixResolver(const+xalanc::XalanDOMString&+++theURI)+:+m_uri(theURI){}

++++virtual+const+xalanc::XalanDOMString*
++++++++getNamespaceForPrefix(const+xalanc::XalanDOMString&+++++prefix)+const+{
++++++++return+&m_uri;
++++}

++++virtual+const+xalanc::XalanDOMString&+++getURI()+const+{
++++++++return+m_uri;
++++}

++++const+xalanc::XalanDOMString++++m_uri;
};

/x:List/x:Fields/x:Field+
/a:List/b:Fields/c:Field+|code-block|syntax|javascript|975429|entityMap^0|0|0|0|0|0|10|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|11|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|12|8|@$J|13|K|14|L|M]]|9|@]|A|$]]|$1|N|3|O|5|6|7|15|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|16|8|@]|9|@]|A|$]]|$1|R|3|S|5|T|7|17|8|@]|9|@]|A|$U|V]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

I've just been having this issue while using Xalan-c

The bit I didn't quite get initially is that the XPath or XSLT namespace aliases/prefixes can be different to that of the document - depending on your namespace resolver.

It appears that if there is a namespace on the doc, then it fails to match a path element unless a namespace is used. (standard but not always followed?)

The XalanDocumentPrefixResolver will map XPath or XSLT namespaces to URI and try and give them id by getting the prefix - where there is no prefix it used the name which turned into xmlns 

<code>/xmlns:List/xmlns:Fields/xmlns:Field</code>

Alternatively you could create your own resolver, but it still requires a minimal namespace used in the xpath :(

Here is one I hacked together while testing, no guarantee of memory

<pre><code>// don't care what prefix given, there can only be the one
struct NoPrefixResolver : public xalanc::PrefixResolver {

 NoPrefixResolver(const xalanc::XalanDOMString&amp; theURI) : m_uri(theURI){}

 virtual const xalanc::XalanDOMString*
 getNamespaceForPrefix(const xalanc::XalanDOMString&amp; prefix) const {
 return &amp;m_uri;
 }

 virtual const xalanc::XalanDOMString&amp; getURI() const {
 return m_uri;
 }

 const xalanc::XalanDOMString m_uri;
};

/x:List/x:Fields/x:Field 
/a:List/b:Fields/c:Field 
</code></pre>

blocks|key|975493|text|如果您可以跳过文档元素，则以下XPath也可以提供帮助：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|975494|//Fields/Field|code-block|syntax|javascript|975495|只要你在任何其他节点下面没有'Fields‘，只要子节点没有命名空间，这种方法就可以工作。|975496|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

If you can skip the document element, the following XPath can also help:

<pre><code>//Fields/Field
</code></pre>

This works as long as you don't have 'Fields' below any other node and as long the sub nodes have no namespace.

I have the following XML:

<pre><code>&lt;List xmlns="http://schemas.microsoft.com/sharepoint/soap/"&gt;
 &lt;Fields&gt;
 &lt;Field&gt;
 &lt;/Field&gt;
 &lt;/Fields&gt;
&lt;/List&gt;
</code></pre>

This is a slimmed down version of XML being returned from a SharePoint web service. I also have the following xPath:

<pre><code>/List/Fields/Field
</code></pre>

When I remove the <code>xmlns</code> from my XML the xPath works fine. When it's in there my xPath finds nothing. Is there something I should be doing differently with my xPath? Modifying the XML is not an option.

Xml Namespace breaking my xpath!

我有以下XML：<List xmlns="http://schemas.microsoft.com/sharepoint/soap/"> <Fields> <Field> </Field> </Fields></List>这是从SharePoint web服务返回的XML的精简版本。我还有以下xPath：/Li...

问Xml命名空间破坏了我的xpath！
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Xml命名空间破坏了我的xpath！EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Xml命名空间破坏了我的xpath！
EN