Even worse, wrapper classes break identity.
更糟的是，包装程序类破坏了身份。
Enhancing the Spring configuration for Axis-aware wrapper classes.
为Axis感知的包装类加强Spring配置。
You should also remove the unused wrapper classes from the EAR file.
您还应该把不用的包装器类从EAR 文件中删除。
Next you will build the service and create the JiBX data bindings wrapper classes.
接下来，我们将构建服务并创建JiBX数据绑定包装类。
Now I'll update the IoC bean definitions for the wrapper classes you just created.
现在我将为您刚才创建的包装类更新IoCbean定义。
These wrapper classes are located in the com.ibm.quickr.meetings.unyte.service package.
这些包装器类位于 com.ibm.quickr.meetings.unyte.service 包。
Now you just need to compile the JiBX binding wrapper classes, as you did for the service.
现在我们只需编译JiBX绑定包装类，与前面构建服务中的编译一样。
In this article, we show you how we created these wrapper classes, which we call widget classes.
在本文中，我们将说明如何创建这些封装器类，我们称这些类为窗口小部件类。
Groovy allows you to create lightweight wrapper classes around interfaces for just this situation.
仅在这种情况下，Groovy允许您围绕接口创建轻量级的包装器类。
In addition, the SDK provides helper wrapper classes to make the core request API calls asynchronous.
此外，SDK提供帮助器封装器类来异步地发出核心请求API调用。
This namespace contains wrapper classes for the data types that conform to the W3C specification.
此命名空间包含符合W3C规范的数据类型的包装类。
I have provided similar wrapper classes for all the IoC beans in the article's source code (see Download).
本文的源代码中，我为所有IoCbean提供了类似的包装类(参见下载)。
Similarly, your system layer may be implemented as an API, a collection of wrapper classes, or as Web services.
相似地，系统层可以作为一个API、包装器类集合或者Web服务实现。
For instance, a database may already have wrapper classes that connect to the database and process SQL statements.
例如，一个数据库可能已经有了连接到数据库并处理sql语句的包装器类。
The control's wrapper classes specify the functions you can use to modify the run-time behavior of the control.
控件的包装类指定可用来修改控件的运行时行为的函数。
Product shape can be customized according to customer requirements: leaded package types, metal wrapper classes.
产品外形可以根据客户要求订做：引线封装类、金属外壳封装类。
For the JiBX binding compiler, I found it easiest to just hide all the BCEL details within several wrapper classes.
对于JiBX绑定编译器，我发现最容易的方式就是把所有BCEL的细节隐藏在几个包装器类中。
The next section describes how to enhance the beans definition in the Spring configuration to reflect these wrapper classes.
下一小节将描述如何加强Spring配置文件中的bean定义来反射这些包装类。
Before you can compile and create the JiBX data bindings wrapper classes, you must first compile the classes themselves.
在编译和创建JiBX数据绑定包装类之前，我们必须首先编译各类。
For more information about the functionality of the wrapper classes, see the object model for the control's base technology.
如需包装函式类别功能的详细资讯，请参阅控制项基本技术的物件模型。
And for both the client and service, you specified JiBX data bindings and successfully created the data bindings wrapper classes for each.
对于客户机和服务，我们都指定了JiBX数据绑定并分别为它们成功地创建了数据绑定包装类。
This latter code example, using the widget wrapper classes, is far more intuitive and takes much less coding to produce the same test case.
后面的代码示例使用了窗口小部件封装器类，看上去要直观得多，并且生成相同测试案例所需的编码要少得多。
Before you can compile and create the JiBX data bindings wrapper classes for the client, you first need to compile the classes themselves.
在为客户机编译和创建JiBX数据绑定包装类之前，我们首先需要编译各类。
On the other hand, to produce the same test automation using the widget wrapper classes, you would simply enter the following five lines of code.
另一方面，要使用窗口小部件封装器类生成相同的测试自动化，只需输入下列五行代码即可。
In cases where an implementation already exists, you can still use an array to expose it as an interoperable Web service by using wrapper classes.
在实现已经存在的情况下，您还可以通过包装器类使用数组来将其作为可互操作的Web服务公开。
In this test process, you'll compile the JiBX binding classes to create wrapper classes, making your data bindings classes a functional part of the overall Web service.
在测试过程中，我们通过编译JiBX绑定类来创建包装类，使数据绑定类成为整个Web服务中的一个功能部分。
The duplicate class structures tend to get in the way, so if you're doing much with BCEL, it may be worthwhile to write wrapper classes that can hide some of these differences.
重复的类结构总有些碍手碍脚，所以如果频繁使用BCEL，那么可能需要编写一个包装器类，它可以隐藏其中一些不同之处。
There are some data wrapper classes and dependent classes in this project to demonstrate typical classpath issues in a real scenario (although their use is superfluous in this project).
在这个工程中有一些数据包装类和从属类用来在真实情景中演示典型的类路径问题(尽管在这个工程中使用它们是多余的)。
The surrounding utility classes and service layer wrapper.
涉及的实用工具类和服务层包装。
Note that for this wrapper we generated life and population into a different package than the original life and population classes.
请注意，对于这个包装器wrapper，我们将life和population生成到不同的包中，而不是最初的life和population类。
应用推荐