这可能非常便利，但是请注意，soap域树通常为您提供了更多的灵活性和控制。
This can be very convenient, but note that the SOAP domain tree in general gives you more flexibility and control.
在域页面上，您可以执行可视警告，以帮助识别需要注意的节点。
On the domain page, you can perform visual alerts to help you identify the nodes that need attention.
您将注意到这个域的名称并完全可见。
现在，如果返回到客户机a的调用，将注意到您并没有影响到任何内容；客户机a启动了一个事务，然后将事务上下文传递给域模型方法。
Now, if you go back to the invocation by Client a, you'll notice that you haven't broken anything; Client a starts a transaction, then passes the transaction context to the domain-model method.
注意，这里适用的逻辑取决于域模型的结构，随着属性的级别和数量增加，操作类中的转换的复杂性也相应增加。
Please note that the logic applied here depends on the structure of the domain model, and as the level and number of attributes increase, the complexity of conversion increases in the action class.
请注意，在图28 中，您需要选择Specifyanotherattribute单选按钮，然后在设置value 域时按Browse。
Notice in Figure 28 that you need to select the Specify another attribute radio button, and then press Browse when setting the valuefield.
注意，GenericDaoHibernateImpl类仅定义一个构造函数，该构造函数接受域类作为其参数。
Note that the GenericDaoHibernateImpl class defines only one constructor that takes a domain class as its argument.
但是注意单参数构造器不是把空链表放入到rest域，这是构建一个只有一个值的链表所必须的。
But notice that the single-argument constructor does not place an empty list into the rest field, as would be necessary to construct a list of one argument.
注意：在 /etc/resolv.conf文件中只能使用一个域条目。
Note: Only one domain entry can be used in the /etc/resolv.conf file.
注意图13中指向acronymlisteditor域的箭头。
Note the arrow pointing to the AcronymListEditor field in figure 13.
注意这个管理和未管理域的列表——默认情况下，所有域都是未管理的。
Notice the list of managed and un-managed domains — by default all domains are un-managed.
注意最好选择应用服务器而不是系统服务器，例如节点代理或是域管理器。
Be careful to select an application server rather than a system server, such as the node agent or domain manager.
请注意，规则主体中可编辑的域都是超链接。
Notice that the editable fields in the rule body are all hyperlinks.
注意，这里定义的名称是在域配置文件元数据中定义过的名称。
Note that the name defined here is the name you defined in your domain configuration file metadata.
注意在其中的某些用例中我们仍然能够使用流作用域的持久化上下文对象。
Note that in some of these use cases we are still able to use the flow-scoped persistence-context object.
注意，正如同置换一样，域引用同样也是动态构成的。
Notice that, just as with substitutions, field references also populate dynamically.
注意- F是由预先定义的FS变量所定义的输入域分隔符。
Note that -f is the input field separator defined by the predefined variable FS.
注意，这个原子域被定义为DOUBLE，而数据库列（由反向工程决定）的数据类型为 BIGINT。
Note that this atomic domain is defined as DOUBLE, while the data type for the database column (determined using reverse engineering) is a BIGINT.
注意，只有当这两台机器(服务器和客户机)属于不同的域时，才必须使用完全限定域名(FQDN)。
Note that a fully qualified domain name (FQDN) is mandatory only if the two machines (the server and the client) are in different domains.
注意，这些只包含应用程序架构的域类(api层)。
Notice that these consist only of the application architecture's domain classes (the API layer).
注意，NFS服务器和客户机的NF s域不一样。
Note that the NFS domain of NFS server and clients are different.
注意，域模型方法并没有包含回滚逻辑。
Notice that the domain-model method does not contain rollback logic.
注意：如果您在查看来自CodeIgniter的消息时遇到困难，这可能是因为您遇到了DNS问题—特别是如果这是一个新的域或子域。
Note: if you're having trouble seeing the generic message from CodeIgniter, it might be that you're having DNS trouble-particularly if this is a new domain or sub-domain.
您可能注意到Photo是在 findById 中通过一个Key 获取的，但是请不要担心它是怎么获得的：在本文中，您只需要将Key看作是封装的id 域。
You might notice that Photos are fetched with a Key in findById, but don't worry about it: For the purpose of this article, just think of Key as a wrapper around the id field.
注意，元素变成了蓝色，value域的背景颜色发生了改变，一些蓝色的箭头图标出现在了响应节点的Testcontents树中(图16)。
Notice that the elements turns blue, the background for the Value field changes color, and that a little blue arrow icon appears in the Test Contents tree on the response node (Figure 16).
在转到Ad控制器之前，您可能注意到了控制器方法直接使用域对象数据访问代码。
Before moving on to the Ad controller, you might have noticed that the controller methods make direct use of domain-object data-access code.
会注意到在相应的域级设置Cookie，因此其它子域不受影响。
Be mindful of setting cookies at the appropriate domain level so other sub-domains are not affected.
注意，在TivoliAccessManager体系结构中，客户端和服务提供者必须是同一kerberos域或具有信任关系的多个kerberos域的成员。
Note that in the Tivoli Access Manager architecture, the client and service provider must be members of the same Kerberos realm or of Kerberos realms that have a trust relationship.
这里需要注意的是，libvirt（及其应用程序）在宿主Linux操作系统（域0）中运行。
Note here that libvirt (and its application) runs in the domain of the host Linux operating system (domain 0).
这里需要注意的是，libvirt（及其应用程序）在宿主Linux操作系统（域0）中运行。
Note here that libvirt (and its application) runs in the domain of the host Linux operating system (domain 0).
应用推荐