blocks|key|4042997|text|只要字符串是有效的+XML，它就不会影响解析器的能力。制表符和换行符被解析器剥离或忽略，实际上是为了满足人类读者的审美感。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|4042998|注您必须将输入流(例如，StringBufferInputStream)传递给DocumentBuilder，因为字符串版本的解析假定它是指向XML。|4042999|entityMap^0|6|3|0|5|3|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

It should not affect the ability of the parser as long as the string is valid XML. Tabs and newlines are stripped out or ignored by parsers and are really for the aesthetics of the human reader.

Note you will have to pass in an input stream (StringBufferInputStream for example) to the DocumentBuilder as the string version of parse assumes it is a URI to the XML.

blocks|key|836477|text|XML字符串的格式应该不会有任何影响，但我记得有一个奇怪的问题，因为我向XML解析器传递了一个长字符串。paser无法解析XML文件，因为它是在一个很长的行中编写的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|836478|如果你插入换行符，这可能会更好，在那种情况下，行不会超过，比如说1000字节。|836479|但不幸的是，我不记得为什么会发生这个错误，也不记得我使用了哪个解析器。|836480|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

There shouldn't be any effect regarding the format of the XML-String, but I can remember a strange problem, as I passed a long String to an XML parser. The paser was unable to parse a XML-File as it was written all in one long line.

It may be better if you insert line-breaks, in that kind, that the lines wold not be longer than, lets say 1000 bytes.

But sadly i do neigther remember why that error occured nor which parser I took.

blocks|key|836497|text|DocumentBuilder为带换行符xml+string和不带换行符的xml+string构建不同的DOM对象。下面是我测试的代码：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|836498|​|836499|StringBuilder+sb+=+new+StringBuilder();
sb.append("<root>").append(newlineChar).append("<A>").append("</A>").append(newlineChar).append("tagB").append("").append("</root>");

DocumentBuilder+builder+=+DocumentBuilderFactory.newInstance().newDocumentBuilder();

InputStream++++xmlInput+=+new+ByteArrayInputStream(sb.toString().getBytes());
Element+documentRoot+=+builder.parse(xmlInput).getDocumentElement();

NodeList+nodes+=+documentRoot.getChildNodes();

System.out.println("How+many+children+does+the+root+have?+=>+"nodes.getLength());

for(int+index+=+0;+index+<+nodes.getLength();+index%2B%2B){
++++System.out.println(nodes.item(index).getLocalName());
}|code-block|syntax|javascript|836500|836501|输出：|836502|How+many+children+does+the+root+have?+=>+4|offset|length|style|CODE|836503|null|836504|A|836505|836506|B|836507|但是，如果从StringBuilder中删除新的newlineChar，则输出为：|836508|How+many+children+does+the+root+have?+=>+2|836509|836510|836511|836512|这表明DocumentBuilder生成的DOM对象是不同的。|836513|entityMap^0|0|0|0|0|0|0|16|0|0|4|0|0|1|0|0|4|0|0|1|0|O|B|0|0|16|0|0|1|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|19|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1A|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1B|8|@]|9|@]|A|$G|H]]|$1|I|3|C|5|6|7|1C|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1D|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1E|8|@$N|1F|O|1G|P|Q]]|9|@]|A|$]]|$1|R|3|S|5|6|7|1H|8|@$N|1I|O|1J|P|Q]]|9|@]|A|$]]|$1|T|3|U|5|6|7|1K|8|@$N|1L|O|1M|P|Q]]|9|@]|A|$]]|$1|V|3|S|5|6|7|1N|8|@$N|1O|O|1P|P|Q]]|9|@]|A|$]]|$1|W|3|X|5|6|7|1Q|8|@$N|1R|O|1S|P|Q]]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1T|8|@$N|1U|O|1V|P|Q]]|9|@]|A|$]]|$1|10|3|11|5|6|7|1W|8|@$N|1X|O|1Y|P|Q]]|9|@]|A|$]]|$1|12|3|U|5|6|7|1Z|8|@$N|20|O|21|P|Q]]|9|@]|A|$]]|$1|13|3|X|5|6|7|22|8|@$N|23|O|24|P|Q]]|9|@]|A|$]]|$1|14|3|C|5|6|7|25|8|@]|9|@]|A|$]]|$1|15|3|16|5|6|7|26|8|@]|9|@]|A|$]]|$1|17|3|-4|5|6|7|27|8|@]|9|@]|A|$]]]|18|$]]

The DocumentBuilder builds different DOM objects for xml string with line feeds and xml string without line feeds. Here is the code I tested:



<pre><code>StringBuilder sb = new StringBuilder();
sb.append("&lt;root&gt;").append(newlineChar).append("&lt;A&gt;").append("&lt;/A&gt;").append(newlineChar).append("&lt;B&gt;tagB").append("&lt;/B&gt;").append("&lt;/root&gt;");

DocumentBuilder builder = DocumentBuilderFactory.newInstance().newDocumentBuilder();

InputStream xmlInput = new ByteArrayInputStream(sb.toString().getBytes());
Element documentRoot = builder.parse(xmlInput).getDocumentElement();

NodeList nodes = documentRoot.getChildNodes();

System.out.println("How many children does the root have? =&gt; "nodes.getLength());

for(int index = 0; index &lt; nodes.getLength(); index++){
 System.out.println(nodes.item(index).getLocalName());
}
</code></pre>



Output: 
<code>
 How many children does the root have? => 4 
 null
 A 
 null 
 B 
</code>

But if the new <code>newlineChar</code> is removed from the StringBuilder,
the ouptput is:
<code>
 How many children does the root have? => 2
 A
 B

</code>

This demonstrates that the DOM objects generated by DocumentBuilder are different.

blocks|key|1582883|text|文档会有所不同。制表符和新行将转换为文本节点。您可以在DocumentBuilderFactory上使用以下方法消除这些问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1582884|1582885|http://download.oracle.com/javase/6/docs/api/javax/xml/parsers/DocumentBuilderFactory.html#setIgnoringElementContentWhitespace(boolean|unordered-list-item|offset|length|1582886|1582887|但是，为了使其正常工作，您必须设置DOM解析器来根据DTD或xml模式验证内容。|1582888|或者，您也可以通过编程方式自行删除多余的空格，方法如下：|1582889|public+static+void+removeEmptyTextNodes(Node+node)+{
++++NodeList+nodeList+=+node.getChildNodes();
++++Node+childNode;
++++for+(int+x+=+nodeList.getLength()+-+1;+x+>=+0;+x--)+{
++++++++childNode+=+nodeList.item(x);
++++++++if+(childNode.getNodeType()+==+Node.TEXT_NODE)+{
++++++++++++if+(childNode.getNodeValue().trim().equals(""))+{
++++++++++++++++node.removeChild(childNode);
++++++++++++}
++++++++}+else+if+(childNode.getNodeType()+==+Node.ELEMENT_NODE)+{
++++++++++++removeEmptyTextNodes(childNode);
++++++++}
++++}
}|code-block|syntax|javascript|1582890|entityMap|0|LINK|mutability|MUTABLE|url|http://download.oracle.com/javase/6/docs/api/javax/xml/parsers/DocumentBuilderFactory.html#setIgnoringElementContentWhitespace(boolean)^0|0|0|0|3Q|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|11|8|@]|9|@$F|12|G|13|1|14]]|A|$]]|$1|H|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|16|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|17|8|@]|9|@]|A|$]]|$1|M|3|N|5|O|7|18|8|@]|9|@]|A|$P|Q]]|$1|R|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|Y]]]]

The documents will be different. Tabs and new lines will be converted into text nodes. You can eliminate these using the following method on DocumentBuilderFactory:

<ul>
<li><a href="http://download.oracle.com/javase/6/docs/api/javax/xml/parsers/DocumentBuilderFactory.html#setIgnoringElementContentWhitespace(boolean" rel="nofollow">http://download.oracle.com/javase/6/docs/api/javax/xml/parsers/DocumentBuilderFactory.html#setIgnoringElementContentWhitespace(boolean</a>)</li>
</ul>

But in order for it to work you must set up your DOM parser to validate the content against a DTD or xml schema.

Alternatively you could programmatically remove the extra whitespace yourself using something like the following:

<pre><code>public static void removeEmptyTextNodes(Node node) {
 NodeList nodeList = node.getChildNodes();
 Node childNode;
 for (int x = nodeList.getLength() - 1; x &gt;= 0; x--) {
 childNode = nodeList.item(x);
 if (childNode.getNodeType() == Node.TEXT_NODE) {
 if (childNode.getNodeValue().trim().equals("")) {
 node.removeChild(childNode);
 }
 } else if (childNode.getNodeType() == Node.ELEMENT_NODE) {
 removeEmptyTextNodes(childNode);
 }
 }
}
</code></pre>

I am currently modifying a piece of code and I am wondering if the way the XML is formatted (tabs and spacing) will affect the way in which it is parsed into the DocumentBuilderFactory class.

In essence the question is...can I pass a big long string with no spacing into the DocumentBuilderFactory or does it need to be formatted in some way?

Thanks in advance, included below is the Class definition from Oracles website.

Class DocumentBuilderFactory

"Defines a factory API that enables applications to obtain a parser that produces DOM object trees from XML documents. "

Xml document to DOM object using DocumentBuilderFactory

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我目前正在修改一段代码，我想知道XML的格式化方式(制表符和空格)是否会影响将其解析为DocumentBuilderFactory类的方式。本质上，问题是is...can，我向DocumentBuilderFactory传递了一个没有空格的长字符串，或者它是否需要以某种方式格式化？提前感谢，下面是来自Oracle网站的...

问使用DocumentBuilderFactory将Xml文档转换为DOM对象
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用DocumentBuilderFactory将Xml文档转换为DOM对象EN