因此，所讨论的场景可能不起作用。
比如，从本系列内讨论的场景可以看到，业务价值的建立体现在。
For example, from the scenarios discussed in this series, the objective was to establish business value in the form of.
在下面讨论的场景中，对FlatFileAdapter的缺省数据绑定进行了自定义，以提供转换解决方案。
In the scenario discussed below, the default data-binding that is part of the Flat File Adapter is customized to provide the transformation solution.
在本文的第2部分中，我们将讨论另外四种场景。
In Part 2 of this article we will discuss four additional scenarios.
如果在测试过程中一切顺利，则围绕场景的讨论可能不会有什么内容。
If things go well during testing, the discussion around a scenario will probably be minimal.
如以前提到的，围绕场景的讨论可能产生新的规范或概要思想。
As mentioned previously, discussions around a scenario could lead to ideas for new specifications or Profiles.
本文将重点讨论八个SOA解决方案场景中的第二个：服务连接性场景。
This article focuses on the second of the eight SOA solution scenarios: the Service Connectivity scenario.
下一篇文章讨论一个完整的业务场景，包含完整的代码。
The next article discusses a complete business scenario that will be fully coded.
本文后面会讨论更复杂的场景。
此部分讨论可能不希望使用WPAR的情况和场景。
This section discusses situations and scenarios where you may not want to use WPARs.
汤姆.克兰西在其1991年出版的小说《恐惧的总和》（又译《惊天核网》）中，预测了这一确切的场景，这引发了公众长时间的讨论。
Tom Clancy predicted this exact scenario in his 1991 potboiler The Sum of All Fears -- and it remains a perennial of public discussion.
文中讨论了应该使用WPAR的各种场景。
The article looked at various scenarios in which WPARs should be used.
暂时回到这集，我需要讨论下最后的场景，就是Sam和Dean在野餐桌边的那幕。
To go back to the episode briefly, I have to discuss that last scene with Sam and Dean at the picnic table.
在我们讨论过的“happypath ”场景中，RentalLocation回答“是”(OK)。
In the "happy path" scenario we are discussing, the RentalLocation replies "yes" (OK).
在这个系列的下一个部分中，我将讨论一些通用的场景，以及与这些场景相关的解决方案模式，同时指出影响这些场景最一般的问题。
In the next part of this series, I will discuss the common scenarios, the relevant solution patterns for these scenarios, and will look at the most common issues affecting these scenarios.
但是，如果不是如预期的那样，则有兴趣的成员将通过场景特定的邮件列表讨论他们的关注内容。
However, if things do not go as expected, then interested members will discuss their concerns through the scenario-specific mailing list.
这些场景的详细信息不在本文档讨论的范围之内。
Details of these scenarios are outside the scope of this document.
现在来讨论在这个场景中提到的设备连接需求。
Now look at the device connectivity requirements I mentioned in the scenario.
除了用于一般主题讨论的WSTF邮件列表外，每个场景还提供其本身的独有邮件列表。
In addition to the WSTF mailing lists for general topic discussions, each scenario provides its own unique mailing list.
场景中的讨论应该覆盖行为表面上的意思。
The discussion in the scene should cover what the action is ostensibly about.
XML已在企业计算中非常流行的前提下，要讨论能用到这一功能包的每一个场景将非常困难。
Given XML is so popular in enterprise computing it's very hard to talk about every scenario in which this feature pack will be used.
此场景是在本系列的第一篇文章中分步构建的；本部分将讨论此场景的关键设计注意事项。
This scenario was built step by step in the first article in this series; this section discusses the key design considerations for the scenario.
在此建模场景中，我们将讨论流程模型中的循环(迭代)行为的表示形式。
In this modeling scenario we discuss the representation of cyclic (iterative) behavior in a process model.
此部分将进一步定义不同类型的工作负载分区，并讨论应该使用WPAR的各个场景。
This section further defines the different types of workload partitions and discusses scenarios where WPARs should be used.
接下来，我将提供一个简单的场景作为基础，并具体讨论前六步涉及的问题。
I'll lay the groundwork next by offering a simple scenario and discussing issues involving the first six steps.
我们将继续第1部分中采用的方法，它给出了最简单的实现场景来演示我们准备讨论的调节功能。
We continue with the approach adopted in Part 1, which involves the presentation of the bare minimum implementation scenario to illustrate our intended throttling capability.
描述了该支持如何通过另一台对等服务器恢复故障服务器的事务日志。讨论了手动和自动对等恢复适用的场景。
It described how this support enables recovery of the transaction log of a failed server by a running peer, and discussed scenarios under which manual and automated peer recovery are appropriate.
编剧可能还需要解决拍摄过程中发生的问题，并与演员讨论角色性格和场景，使演员对所要拍摄的场景有更好的了解。
The screenwriter may also work with the problem, discussing the characters or situations in the screenplay to give the actors a better sense of the vision.
本文中所讨论的GDD场景是各个组织今天正在使用或考虑使用的更加常规的模型。
The GDD scenario we've worked through in this article is one of the more common models that organizations are using or contemplating today.
这就是第8章的结尾8,这些场景从讨论演变成一场争斗，演变成吵架，演变成分歧。
This is the end of Chapter 8 which is one of these scenes of a discussion turning into fight, turning into a brawl,turning into a division.
应用推荐