这又会减轻集成挑战，并减少供应商绑定。
This will in turn ease integration challenges, and reduce vendor tie-in.
对于绑定名称，适当的命名服务维护将允许您将对象从任一供应商绑定到您的jndi树，因而尽管供应商可能改变，但绑定名称却不必改变。
In the case of the binding name, proper naming service maintenance will allow you to bind objects into your JNDI tree from any vendor, so while the vendor may change, the binding name doesn't have to.
通过创建连接工厂，预先配置它然后将它绑定到命名服务，您可以在消息传递服务中隐藏特定于供应商的连接参数。
By creating a connection factory, pre-configuring it, and binding it to your naming service you can conceal vendor-specific connection parameters in your messaging service.
当然，供应商们偏爱不完善的互操作性，因为这样可以将用户绑定在它们的私有产品之上。
Of course, the vendors love imperfect interoperability because it locks customers into their proprietary offerings.
然而，根据定义，本地home接口只能由本地容器访问，所以供应商不需要将它们绑定到全局JNDI命名空间中。
However, by definition, local home interfaces can only be accessed by the local container, so vendors do not need to bind them to the global JNDI namespace.
上面的示例代码中含有一个特定于Xerces的类，但是其他方法不会像它一样与某个特定的供应商类紧密绑定在一起。
The example above includes a Xerces-specific class in the code, but other ways aren't as tightly tied in to a specific vendor class.
在使用Web应用程序的情况下，是使用特定于供应商的部署描述符扩展来指定这个绑定，清单4中显示了一个这样的例子。
In the case of a Web application, a vendor-specific deployment descriptor extension is used to specify this binding, an example of which is shown in Listing 4.
所有使用Linux的用户，都不会受到任何商业供应商的绑定，将你锁定在某些产品或服务协议中。
With Linux, there is no commercial vendor trying to lock you into certain products or protocols.
所有使用Linux的用户，都不会受到任何商业供应商的绑定，将你锁定在某些产品或服务协议中。
With Linux, there is no commercial vendor trying to lock you into certain products or protocols.
应用推荐