It is often hard to even get the code of components developed by other internal teams within the same organization.
它通常很难平等地获取由其它相同组织中的外部小组开发的控件代码。
This pattern encapsulates code for accessing components through directory services, such as JNDI client code, so that a client can simply pass in the name of a resource and get back that resource.
这个模式通过目录服务封装访问组件的代码，如JNDI客户端代码之类，因此客户端可以简单的以资源名通过验证并返回这个资源。
A balanced implementation that USES all the components to the fullest of their capabilities requires less hardware and less code.
充分使用了所有组件功能的均衡实现就不会需要那么多的硬件和代码。
There are lots of systems that follow this pattern, where you write some modules / components in source code then describe how they are connected using an external config file.
许多系统都遵循这种模式，在这些系统中，你编写一些模块/组件，然后通过一个外部配置文件定义他们之间的连接。
For each of those business item attributes, the code determines which processes or components the attributes serve as inputs to or outputs of and makes a list of these dependent processes.
对于那些业务项目属性，代码确定这些属性充当哪些流程或组件的输入或输出，并制作这些相关流程的列表。
These might be in the form of both paper documentation and actual running code (components) that may be reused.
他们应当以文档和实际执行代码（组件）的方式，这样可以重用。
Object types allow you to separate (decouple) the components of a system from one another, which makes for reusable, extensible, and scalable code.
对象类型允许将系统中的组件相互分离，从而得到可重用、可扩展和可伸缩的代码。
Provide a detailed implementation discussion, including example code and other appropriate solution artifacts, on a set of critical components on which core elements of the solution are based.
针对解决方案的核心元素所基于的关键组件集提供详细的实现讨论，包括示例代码以及其他适当的解决方案工件。
Because components don't interoperate at a code level, traditional methods of unit testing are not necessarily appropriate.
由于组件不能在代码级别进行互操作，因此不适合使用传统的单元测试方法。
The ovals represent data or objects, and the rectangles represent bits of code or components.
椭圆表示数据或对象，矩形表示代码或组件的位。
There are some deeper differences under the covers, including the use of two separate hierarchies of components within BCEL — one for inspecting existing code and the other for creating new code.
除了表面上的差别，还有一些更深层的区别，包括在BCEL中组件的两个不同层次结构的使用——一个用于检查现有的代码，另一个用于创建新代码。
If there is not a build server in place, a simple test of your scripts can be to extract the necessary code components run the scripts.
如果没有配备构建服务器，可以进行简单的脚本测试，提取必要的代码组件来运行脚本。
The answer to both of these problems lies in dividing the code into appropriate components that can be built, tested, and deployed separately.
解决这些问题的方案就是：将代码根据编译、测试和部署分类为不同的组件。
So we also generate the code that is necessary to run the components (incl. their technology-neutral implementation) on the implementation technology of choice.
因此，我们用选定的实现技术生成了运行组件(及组件的技术中立的实现)所必需的代码。
Reusable components are simply pre-built pieces of programming code designed to do a specific function.
可重用组件只不过是针对特定功能而设计的、预建的程序代码块。
In one case proper use of EJB components resulted in less, and more easily understood code.
在一个例子中ejb组件的正确使用使得代码更简洁、更易懂。
An analogous situation can happen when code is refactored to collapse the code base down to a more carefully rationalized set of routines or components.
类似的情况出现在当重构代码，将代码基数分为更谨慎地合理的程序或组件集合的时候。
Programmers want to leverage deep libraries of prebuilt components complete with clean APIs, documentation of best practices, and code samples.
程序员需要在使用简洁的API所开发出来的预制组件的库，最佳实践的文档和代码示例之间取得均衡。
An approach for exporting annotations out of code and into the model using pre-existing components as well as new scripts was defined as well (R6).
一种使用预先存在的组成要素从代码中将注释导出到模型中的方法也被定义好了(R 6)。
The source code for all of the open source components included in WAS CE is available.
WAS CE中包含的所有开放源码组件的源代码都可以获得。
Components also point at the chunk of code that provides the implementation of the service.
组件还指向提供服务实现的代码块。
The creation of wrapper-facades for these components hid the details of complex interactions between the legacy components, and also provided an abstraction that protected new code from legacy code.
为这些组件创建包装外观，会隐藏遗留组件间复杂的交互细节，并提供了一个抽象，使新旧代码不致混淆。
The renderers of those components generate the HTML code (shown in Listing 2), which contains the form elements.
这些组件的呈现程序生成含有表单元素的HTML代码(见清单2)。
Dojo widgets are Ajax-based UI components that can be reused with a single line of HTML code.
Dojo小部件是基于Ajax的UI组件，可用一行html代码重用。
This will consist of the Team Area, various streams (such as code, integration, and so forth), components, work items, and more.
这将包括TeamArea，各种流程(比如代码，整合，等等)，组件，工作条目等等。
Finally, you can find many blogs and other Web sites that showcase amazing Flex components, often with source code-i've listed some of these in the resources section as well.
最后，您可以找到许多其他博客和Web站点，它们展示了令人称奇的Flex组件，甚至还常常包含源代码——我在参考资料小节列出了其中一部分。
Both make extensive use of OSGi for the organization of code into functional components and the reuse of that code on both the server and client tiers.
从功能组件中的代码组织到客户层和服务器层代码重用，都广泛地使用了OSGi。
In the following sections, we will look inside the PHP code snippets that make up each of these components. Figure 2 depicts an overview of these functional components.
在后续章节，我们将深入探索组成这些组件的各个php代码片段。
You can build each of these components with literally a line or two of code using Tapestry.
使用Tapestry，只需要一两行代码就可以构建这些组件。
All of the sources including code, documents, and configuration files should be divided into several components.
所有的资源包括代码，文档和配置文档都应该划分成几个组件。
应用推荐