扩展容器：通用容器服务方法。
Extending containers: Approach for common container services.
无法在多个EJB组件中应用容器服务
No way to apply container services across multiple EJB components
这些容器服务器应该分布在多台机器上。
These container servers should be spread over multiple machines.
有关详细信息，请参阅侧栏其他客户机容器服务。
See the sidebar Other client container services for more information.
传统JEE应用程序依赖于容器服务，并且使用。
Traditional JEE applications depend on container services and use.
EJB 3.0规范将使用注解来应用容器服务。
The EJB 3.0 specification will use annotations to apply container services. Here is an example of how you would specify a transactional attribute on a stateless session bean.
此虚拟容器服务用于自定义ui虚拟化行为。
The virtual container service is used to customize the UI virtualization behavior.
它们如何与容器服务(例如，数据库持久化服务)交互？
How do they interact with container services (e.g., the database persistence service)?
EJB 3.0规范使用标注（和XML）来应用容器服务。
The EJB 3.0 specification uses annotations (in addition to XML) to apply container services.
如果一次能在许多EJB的定义中应用容器服务，这样情况会好些。
It would be nice if I could apply container services one time across many EJB definitions.
表示一个与编辑上下文和设计视图相关联的虚拟容器服务。
Represents a virtual container service associated with an editing context and design view.
在101个分区和一个容器服务器的情况下，最多能包含2GB的项。
With 101 partitions and one container server, you can have up to 2 GB of items.
若要扩展，您只需要启动另一个容器服务器，最好在另一个机器上，以分担负载。
To expand, you just start another container server, preferably on another machine to spread the load.
修改现有的容器服务以匹配云资源和云任务模式，并尽可能以非侵入方式将它们附加到应用程序上。
Modify the existing container services to match the cloud resource and cloud task patterns and attach them to the application in as non-intrusive manner as possible.
EJB组件设计用于封装业务逻辑，并同时将所有的复杂性隐藏在Bean和内置ejb容器服务后。
EJB components are designed to encapsulate the business logic while hiding all complexity behind the bean and built-in EJB container services.
还可以使用XML部署描述符应用容器服务，而XML部署描述符可以在部署时覆盖启用灵活性的标注。
Container services can also be applied using XML deployment descriptors, which can also provide an override for annotations enabling flexibility at deployment time.
在 101 个分区，101 个容器服务器的情况下，您以供可以保存 202GB 的项。
With 101 partitions, you can scale up to 101 container servers for a total of 202 GB of items.
本文概括的提出了一些设计策略和模式，它们可以帮助您在容器服务中实现云特征，以及帮助您将应用程序移植到云上。
The methodology we have outlined provides design strategies and patterns to help you enable cloud characteristics in container services and to help you migrate applications to the cloud.
CDI包含一个cdi容器服务，该服务根据应用程序作用域声明自动管理作用域；容器根据需要创建和销毁CDIbean。
CDI includes a CDI container service that manages scope automatically depending on the application scope declaration; CDI beans are created and destroyed on demand by the container.
我们将托管资源和托管任务模式转变成云资源和云任务模式，以便向您介绍如何将容器服务扩展为云应用程序使用的服务。
we have adapted the managed resource and managed task patterns into cloud resource and cloud task patterns to show you how to extend container services to be used by cloud applications.
这种类型的MBean用于代表动态环境中的目录服务器和静态环境中的容器服务器(与ObjectGrid之前的版本不同)。
This type of MBean is used to represent catalog servers in a dynamic environment and container servers in a static environment (unlike previous versions of ObjectGrid).
该应用程序服务器支持使用诸如jms(包括MQ JMS连接)、Web服务、J2EE容器服务、JDBC数据库访问等技术。
The application server enables the use of technologies like JMS (including MQ JMS connectivity), Web services, J2EE Container services, JDBC database access and so forth.
如果将这种类比应用到WebSphereeXtremeScale，您可以将文件柜看做在JVM中运行的容器服务器。
If you extend this analogy to WebSphere eXtreme Scale, you can compare a file cabinet to a container server, which runs in a JVM.
在创建了服务容器之后，宿主将它自己的服务添加到提供程序中，如图6所示。
After the service container is created, the host adds its own services to the provider, as shown in Figure 6.
服务关联——轻量级容器提供一种将服务与容器中的对象相关联的方法。
Service attachment — Lightweight containers provide a way to attach services to the objects in the container.
在部署阶段，不同版本的服务将在存储库中进行发布，并在带有集成业务流程的服务容器中进行部署。
In the deploy phase, different versions of services are published in repositories and deployed in service containers with an integrated business processes.
在容器之外测试服务层也变得非常容易，从而极大地加速了开发周期。
Testing the service layer outside the container also becomes very easy, which can significantly speed up the development cycle.
最后，我们将给出使用每种类型的对象和它提供的容器管理服务的一些最佳实践。
We'll close with a list of best practices for using each type of object and the container-managed services it provides.
最后一步是，服务提供者将代码部署到服务容器(应用服务器、SOAP服务器)中，这样就可以首选使用HTTP上的SOAP访问代码。
As a final step, the service provider deploys the code in a service container (application server, SOAP server), so that it can be accessed preferably using SOAP over HTTP.
最后一步是，服务提供者将代码部署到服务容器(应用服务器、SOAP服务器)中，这样就可以首选使用HTTP上的SOAP访问代码。
As a final step, the service provider deploys the code in a service container (application server, SOAP server), so that it can be accessed preferably using SOAP over HTTP.
应用推荐