dom4j

The dom4j tool requires little effort , as you 'll now see .

您将看到，dom4j工具仅需要很少的工作即可完成解析。

By using different factories for the dom4j document build you can get documents constructed from different families of components .

通过使用不同工厂进行dom4j文档构建，您能获取不同系列的组件中构造的文档。

Based on the present implementations I 'd recommend dom4j rather than JDOM for anyone starting a new project .

基于当前实现，我愿为着手新项目的人们推荐dom4j，而不是JDOM。

The tool you 'll use here is dom4j , which allows you to parse XML data into a Java object .

本文中使用的工具是dom4j，该工具允许您将XML数据解析为一个Java对象。

Dom4j is again the clear best , and AXIOM the worst by a considerable margin .

dom4j又是最好的，而AXIOM则比其他的差了一大截。

Clients then use some scheme to transfer these files into local storage , and you can use dom4j to parse and modify the file data .

客户机随后使用某种模式将这些文件传递到本地存储中，然后您可以使用dom4j解析并修改文件数据。

The grunt work is handled by dom4j .

这些工作都是由dom4j处理的。

Given dom4j 's performance , stability , and feature-set advantages , you should consider it a strong candidate for most projects .

考虑到dom4j的性能、稳定性和特性设置的优点，您应把它当作多数项目中的一个有力的候选者。

On memory use , dom4j is again best , but in this contest AXIOM is the undisputed loser .

在内存使用方面，dom4j又是最好的，而AXIOM在这方面是毫无争议的失败者。

The top-level code for dom4j is a little more involved than that for JDOM , but it works along very similar lines .

dom4j的顶级代码比JDOM的稍微复杂些，但是它们的代码行非常类似。

As with DOM and dom4j , before doing anything with AXIOM you need to get a factory that builds the component objects of the model .

与使用DOM和dom4j一样，在使用AXIOM进行任何工作之前，您需要获得一个构建模型组件对象的工厂。

JAXB , Quick , and Zeus all turn in respectable performance figures compared to dom4j , but take nearly twice as long as JiBX overall .

与dom4j相比，JAXB、Quick和Zeus都获得了不错的性能数字，但是所花费的时间整体来说都几乎是JiBX的两倍。

Among the three leading contenders in the ease of use category , dom4j differs from the others in using an interface-based approach with multiple layers of inheritance .

就使用方便这一范畴而言，在JDOM、dom4j和ElectricXML这三个主要竞争者中，dom4j与其它两个的区别在于它使用带有多个继承层的基于接口的方法。

Dom4j offers better performance than any of the data binding approaches in this area , beating JiBX by a smidgen and Zeus by not much more .

在该领域中，dom4j提供的性能是所有数据绑定方法中最好的，比JiBX稍好一点，比Zeus更加好一点。

Dom4j combines DOM-like interfaces with Java collections classes for a very flexible API that offers a lot of power & at the cost of some complexity .

dom4j将类似DOM的接口和Java集合类组合到一起，这种非常灵活的API提供了很多强大的功能，但却在一定的程度上增加了复杂性。

One potential use is to allow portions of a document to be mapped to and from a document model ( such as DOM , JDOM , or dom4j ) .

一种可能的用法就是允许在部分文档和文档模型（例如DOM、JDOM或dom4j）之间相互映射。

There 's not nearly as much variation here as in the input tests , though the fact that dom4j does better than any of the data binding frameworks suggests that they all still have room for improvement .

尽管这里的结果与输入测试的几乎没有太大的变化，但是dom4j的确优于其它任何数据绑定框架的这一事实表明它们仍然有改进的余地。

JDOM , dom4j , and Electric XML all come across in these code samples as about equally easy to use , with EXML perhaps the easiest and dom4j the more difficult by small margins .

dom4j和ElectricXML都得到这些几乎同样易于使用的代码样本，其中EXML可能最简单，而dom4j受一些小条件限制而较困难。

I have seen many requests for a comparison of SAX , DOM , JDOM , and dom4j to JAXP , but making such comparisons is impossible because the first four APIs serve a completely different purpose from JAXP .

我曾经看到过许多关于将SAX、DOM、JDOM和dom4j与JAXP进行比较的请求，但作这样的比较是不可能的，因为前面四个API与JAXP具有完全不同的用途。