使用定制文档模型的索引定义。
为文档模型的目标创建一个DDO。
如果使用定制的文档模型,就可以。
为什么需要另一种文档模型?
用户定义的定制文档模型。
利用定制文档模型搜索结构
AXIOM与其他文档模型有许多相似之处。
NSE文档模型揭秘。
访问器api提供对状态文档模型类型化的访问。
The Accessor API provides typed access to the state document model.
这种虚拟的文档模型工作于XML文档的元素级。
This virtual document model works at the level of elements in the XML document.
访问器直接对状态文档模型中的各个位置进行读写。
The accessors read directly from, or write to, the respective positions in the state document model.
然后,在软件架构文档模型中使用以下方法创建图。
Then, just create diagrams in the Software Architecture Document model using these approaches.
图2表明了状态容器实际是非类型化文档模型的包装。
Figure 2 shows that the state holder is a wrapper enclosing the un-typed document model.
Web服务的类型、复杂性、文档模型、扩展和性能。
Types, complexity, document model, extension, and performance of Web services.
根据默认文档模型的性质,可以猜到它定义为下面这样。
Bearing the characteristics of the default document model in mind, it is defined as.
在创建索引时指定的文档模型参数指定模型文件的根元素。
The document model parameter specified at index creation time specifies the root element in the model file.
图5针对产品数据(参见清单1)定义了一个定制文档模型。
Figure 5 defines a custom document model on the basis of the product data (refer to Listing 1).
这个文档模型存储在文件nsemodel . xml中。
您可以确定一个已知的文档模型,或者作为一般文档。
You can either identify a known document model or aim to be generic.
“文档”栏指定了支持拉或文档模型API(如dom)的解析器。
The doc column specifies parsers that support a pull or document model API, like DOM.
一般来说,处理任意的XML的最简单方法是使用某种形式的文档模型。
Generally speaking, the easiest way to work with arbitrary XML is by using a document model of one form or another.
所需的导航状态信息位于状态文档模型中,被封装为专用访问器工厂实现。
The required navigational state information is located in the state document model and is encapsulated in the dedicated accessor factory implementation.
这个类用来代表外部xml节点,这些节点保留在文档模型中,并不被忽略。
This class is used to represent the foreign XML nodes, which remain in the document model and aren't neglected.
Compass编辑器之间的公共文档模型允许您轻松快捷地完成这种分配。
The common document model between the Compass editors enables you to do this assignment quickly and easily.
要使用定制的文档模型,就必须在创建文本索引时指定一个文档模型。
To use a custom document model, you have to specify one at text index creation time.
这些结果涉及了生成代码方法和映射绑定方法,为了进行比较,包含了文档模型。
These results cover both generated code and mapped binding approaches, with document models included for comparison.
用于将软件与xml解析器结合的两种常用API模型是:文档模型和事件模型。
Two common API models exist for interfacing software with an XML parser: the document model and the event model.
这正是文档模型的任务所在,即不对该XML的形式进行任何假设,如实地表示XML。
That's the whole point of a document model, after all — to faithfully represent XML without any assumptions about the form of that XML.
理想的方法是在SOAP框架中同时使用这两种技术,但普通的文档模型不支持这种用法。
The ideal approach would be to combine the two techniques within the SOAP framework, but normal document models aren't set up to allow this.
如果架构文档模型文件同其他的模型文件一并被分发到读者的话,这一技术将会很好的发挥作用。
This technique will work well if the architecture document model file is to be distributed to readers along with the other model files.
应用推荐