内容组件、库组件、内容组件容器和内容接口。
Content components, library components, content component container, and content interfaces.
详述如何扩展组件容器来实现自定义功能。
Details how to extend component containers to implement custom functionality.
记住，我们期望通过某种组件容器或中间件平台运行组件。
Remember that we expect some kind of component container or middleware platform to run the components.
因此，在组件容器开发过程中大规模复用已有的软件资产变得非常重要。
Hence, it's becoming more and more important to reuse existing software assets when developing component containers.
CAI包含一个业务组件容器来管理业务组件的生命周期，考虑一个业务组件生命周期的以下5个阶段。
CAI contains a business component container to manage the lifecycle of business components. Consider these five phases in the lifecycle of a business component.
然后给出了一个组件容器的产品线——PLACE的设计，解释了其两个主要部分：产品线体系结构和产品派生流程；
The authors present product line architecture and product derivation process which comprise a product line of component container, named PLACE.
唯一需要的组件是6英尺长的塑料管和一个接水的容器。
The only components required, are six feet of plastic tube, and a container to catch the water.
现在无需对每个组件进行资源扫描，我们只需做一次即可，可以将工作委托给各种容器组件实现。
Instead of doing the resource scanning for every component, we just do it once, properly delegating the work to various container components.
在设计时上下文中，组件和它的容器之间的关系是通过站点建立的。
In a design-time context, the relationship between a component and its container is established through a site.
通常，这些组件没有容器不能运行，并要求您在测试前和拆卸后执行特殊设置。
Normally, these components don't run without a container, requiring you to perform special setup before testing and teardown afterward.
应用程序的每个组件都是在容器中运行的。
文档图标是作为基于卡片的应用程序和组件的容器使用的ADIEU 表格。
The document icons are ADIEU sheets that serve as containers for card-based applications and components.
因此，容器组件的实例可以拥有任意数量的属性和操作，具体取决于使用场景。
Thus, instances of container components can have arbitrary amounts of properties and actions, depending on the situation in which they are used.
将您的组件放入该容器后，容器会为您处理一些事情。
You put your component into the container, and the container does something for you.
正如您可以看到的那样，组件刚好由一个容器管理，并且每个组件刚好具有一个站点。
As you can see, a component is managed by exactly one container and each component has exactly one site.
当组件允许容器取得它的所有权时，该组件就获得了对该容器所提供的服务的访问权。
When a component allows a container to take ownership of it, the component gains access to the services provided by that container.
与复合应用程序中的常规组件相比，容器组件并不包含定义属性和操作的静态WSDL文件。
In contrast to regular components used in composite applications, a container component doesn't have a static WSDL file that defines its properties and actions.
现代组件体系结构假定组件在称为容器的中间件环境中执行。
Modern component architectures assume that components execute in middleware environments called containers.
它也有包含组件的容器，容器也是组件，也可以由其他容器包含。
It also has containers that contain components, and that also are components that can be contained by other containers.
模型VOB容器能够存储多模型组件；部署VOB容器能够存储可部署资产的多组件。
A model VOB container can store multiple model components; a deployment VOB container can store multiple components of deployable assets.
使用外部配置文件(通常是XML)，可以将要部署的组件映射到容器环境。
Deployed components are mapped to the container environment using external (usually XML) configuration files.
容器包含组件，并且允许所包含的组件相互访问。
A container contains components and allows contained components to access each other.
这些容器组件可以方便地把相似、相关的组件分组在一起。
These container components are an easy way to group similar, related components together.
在将组件放到窗体中时，设计器宿主会为该组件和它的容器创建一个站点实例。
When you place a component on a form, the designer-host creates a site instance for the component and its container.
它充当HTML标记和组件的容器。
位置是所有页面和组件的顶层容器。
A place is a top-level container for all the pages and components.
容器独立性：在托管组件环境中，组件承载在容器中。
Container independence: in a managed component environment, components are hosted within a container.
容器组件配置的主要组成就是地标表示。
The main part that configures a container component is the concept of a landmark expression.
组件的示例有列容器、行容器和控件。
Examples of components are column containers, row containers, and controls.
本文介绍了通用应用程序容器框架及其容器组件的基本概念。
This article gives an introduction to the basic concepts of the generic application container framework and its container components.
应用推荐