您还应该把不用的包装器类从EAR文件中删除。
You should also remove the unused wrapper classes from the EAR file.
包装器类还在必要时处理xsl转换、名称空间和模式检验。
The wrapper class also handles XSL transformations, namespaces and schema validation if needed.
为了在递归方法中传递，匿名类应该扩展方法已知的包装器类型。
To pass this to a recursive method, the anonymous class should extend a wrapper type known to the method.
仅在这种情况下，Groovy允许您围绕接口创建轻量级的包装器类。
Groovy allows you to create lightweight wrapper classes around interfaces for just this situation.
例如，一个数据库可能已经有了连接到数据库并处理sql语句的包装器类。
For instance, a database may already have wrapper classes that connect to the database and process SQL statements.
相似地，系统层可以作为一个API、包装器类集合或者Web服务实现。
Similarly, your system layer may be implemented as an API, a collection of wrapper classes, or as Web services.
我们创建一个称为HeaderCell的包装器类，用于区分标题栏单元格和内容单元格。
We created a wrapper class, called HeaderCell to distinguish a header cell form a content cell.
清单9给出了这个包装器类，在示例应用程序中称为RepositoryWrapper。
Listing 9 shows the wrapper class, which is named RepositoryWrapper in the sample application.
在实现已经存在的情况下，您还可以通过包装器类使用数组来将其作为可互操作的Web服务公开。
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.
自动装箱：编译器不生成对包装器类的value Of方法的调用，而是生成对构造函数的调用。
Autoboxing: Rather than generating calls to the valueOf method in the wrapper class, the compiler generates calls to the constructor instead.
对于JiBX绑定编译器，我发现最容易的方式就是把所有BCEL的细节隐藏在几个包装器类中。
For the JiBX binding compiler, I found it easiest to just hide all the BCEL details within several wrapper classes.
如果需要其他的数据类型，比如说整数、浮点数或者布尔值，必须使用相应的包装器类来解析字符串。
If you need another data type such as integer, floating point, or Boolean value, you will have to parse the string using the appropriate wrapper class.
处理这种情况的一个相对简单的方法是以您的服务实现为基础创建包装器类，将该集合接口转换成一个数组接口。
One relatively easy way of dealing with this situation is to create a wrapper around your service implementation, converting the collection interface into an array interface.
现在，我们可以基于这个包装器类来创建适当的Web服务构件了，它在内部使用现有的基于集合的实现。
Now you can create the appropriate Web services artifacts based on this wrapper class, which internally USES the existing collection-based implementation.
这些包装器类位于 com.ibm.quickr.meetings.unyte.service包。
These wrapper classes are located in the com.ibm.quickr.meetings.unyte.service package.
为了打开到blog的连接，我们围绕XML - RPC连接创建一个新的包装器类，它实现两个必需的功能。
Back to the issue of opening up the connection to your blog, you'll produce a system by creating a new wrapper class around the XML-RPC connection that resolves the two necessary functions.
重复的类结构总有些碍手碍脚，所以如果频繁使用BCEL，那么可能需要编写一个包装器类，它可以隐藏其中一些不同之处。
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.
第一个助手是位于代码段顶部的处理程序panel，这是带有 panel 类的div标记的包装器。
The first of these is the handler panel at the top of the code segment, which is a wrapper for a div tag with the class panel.
Message类是个包装器，包装被处理消息的有效负载。
The message class is a wrapper around the payload of the message being processed.
以下这个类提供了文本文件的包装器，在遍历它的时候，它将列出文件中的每行内容。
This class provides a wrapper over a text file that lists each line of a file as it is iterated over.
把BCEL细节隐藏在包装器中，也提供了方便地添加更多功能的位置，就像在类和方法比较代码中一样。
Hiding the BCEL details in my wrapper also gave me convenient places to add more functionality, as in the class and method comparison code.
清单2和清单3是一个简单的PHP应用程序，其中包含一个类、方法和一些包装器代码。
Listing 2 and Listing 3 show a simple PHP application with a class, methods, and some wrapper code.
同步的集合包装器以及早期的Hashtable和Vector类带来的更大的问题是，它们在单个的锁上进行同步。
The bigger problem with the synchronized Collections wrappers, and the earlier Hashtable and Vector classes, is that they synchronize on a single lock.
为了方便起见，可以将这些技术组合成一个类包装器。
You might combine these techniques into a class wrapper for convenience, using some magic methods.
这是一个非常简单的包装器，打包了feedlist类的add方法。
This is a very simple wrapper around the add method on the FeedList class.
这些action类为应用程序的model层提供了一个接口，充当围绕业务逻辑的包装器。
These Action classes provide an interface to the application's Model layer, acting as a wrapper around the business logic.
在这个快照中，右上角的大帧显示了添加到stringbuilder类中的计时包装器方法的分解。
In this shot the large frame in the upper right shows the disassembly of the timing wrapper method added to the StringBuilder class.
尽管Dictionary类当前与关联数组的包装器相差无几，但这里有一些了解对象功能的线索。
Even though the Dictionary class is currently little more than a wrapper around an associative array, there is some clue to the power of objects here.
清单1给出了StringArray类的源代码，这个类是String有序数组的一个包装器。
Listing 1 gives the source code for my StringArray class, a wrapper for ordered arrays of Strings.
还有一个poid类，它是poid值的简单包装器，它使API与实际的值类型相分离(在这里是最初为long)。
There is a POID class, a simple wrapper for the POID value, which insulates our APIs from the actual value type (primitive long in this case).
应用推荐