组合业务服务经常需要结合使用以文档为中心的活动和支持SOA的业务流程。
Composite business services often require a combination of document-centric activities and SOA-enabled business processes.
软件架构师创建了差距分析文档，这个文档对新业务过程的需求和现有服务组合进行了比较。
The Software Architect creates a gap analysis document that compares the requirements of the new business process against the existing service portfolio.
为了避免此反模式，需要集中精力进行设计重构，以将各个数据片断组合到一个文档中，以消除通信量过多的服务。
To avoid this antipattern, a focused effort should be on refactoring the design to combine individual pieces of data in one document thus eliminating the chatty services.
我们的数据库具有一些服务，能够帮助把XML文档分解成关系表结构和从关系表结构组合成XML文档。
Our databases have services that help shred and compose XML documents to and from relational table structures.
虽然在RosettaNet环境中，它不是一个大问题，但是在实现Web服务时，需要将这些DTD中的模式组合到同一个文档中。
While this is not a big problem in the RosettaNet environment, with Web services, the schemas from these DTDs need to be combined into the same document.
但是如果在同一文档中组合使用这些元素类型，比方说在部门、部门地址及其Web服务器的列表中，会怎么样呢？
But what if they are combined in the same document, such as a list of departments, their addresses, and their Web servers?
但是如果在同一文档中组合使用这些元素类型，比方说在部门、部门地址及其Web服务器的列表中，会怎么样呢？
But what if they are combined in the same document, such as a list of departments, their addresses, and their Web servers?
应用推荐