Caching isn't even the main point of the Service Locator pattern.
缓存甚至不是Service Locator模式的主要点。
This article assumes knowledge of the Service Locator pattern.
本文假定的服务定位器模式的知识。
We will briefly review how JNDI works here, primarily to understand the parts that affect the Service Locator pattern.
我们将主要回顾JNDI是如何工作的，首先要弄清楚影响Service Locator模式的部分。
The Service Locator pattern is still useful for encapsulating the code that uses JNDI, even if the locator does not use caching.
Service Locator模式对封装使用JNDI的代码仍然有用，即使定位器不使用缓存。
In addition, the Service Locator pattern can be modified to access the appropriate version of the EJB home and remote interfaces.
另外，可以通过修改Service Locator模式来访问合适版本的ejb本地及远程接口。
When the Service Locator pattern was first developed for J2EE 1.2, caching references was a good idea, or at least it didn't hurt anything.
当在J2EE 1.2中首次使用Service Locator模式开发时，缓存引用是一个很好的主意，或者说至少在当时没有任何的伤害。
To access the business services (lets say in the Spring layer), the AjaxBean can make use of service Locator pattern to interact with the business services.
为了访问业务服务(比如说在Spring层)，AjaxBean可以使用Service Locator模式与业务服务交互。
When the Service Locator pattern was first developed for J2EE 1.2, caching resource references was a good idea because JNDI lookups were often slow and hurt performance.
当首次使用Service Locator模式开发J2EE 1.2应用程序时，因为JNDI查找时常降低甚至有损于执行性能，所以缓存资源引用在当时是一个很好的主意。
The Service Locator pattern addresses this challenge by providing a repository for all services that the RIA requires. Within it you can centralize and reuse your service tags.
服务定位器模式通过提供一个RIA所需的所有服务的仓库解决这个难题。使用它，你可以集中和重用你的服务标签。
The service Locator pattern (see resources) is a well-known J2EE application design pattern that encapsulates the code needed to lookup resources through directory services such as JNDI.
Service Locator模式(参见参考资料)是J2EE应用程序中著名的设计模式，它封装了需要通过目录服务(如JNDI)查找资源的代码。
Use of the service locator design pattern to simplify lookup code.
使用服务定位器设计模式来简化代码。
Use of the service locator design pattern to simplify lookup code.
使用服务定位器设计模式来简化代码。
应用推荐