清单3：一个代理服务的客户端类。
清单11首先创建了一个新的客户端类。
这个客户端类如清单2所示。
RPC代理的客户端类也在这个包中。
The client-site classes for the RPC proxy are also located in this package.
用户下一步需要完成的事情就是WMQTT客户端类的实现。
The next thing you need is an implementation of the WMQTT client classes.
接口编写好后，准备编写调用该接口公开的方法的客户端类。
With the interface written, you are ready to write the client class that calls the methods that the interface exposes.
对于POST请求，创建一个客户端类Client。
在客户端类中，取消清单24中addheader调用的注释。
In the client class, uncomment the addHeader invocation in Listing 24.
您必须使EJB远程接口的客户端类对应用程序类加载器可用。
You must make the client classes of the EJB remote interfaces available to the Web application class loader. This can be done in two ways.
此时，您应该有一个客户端类、一个接口、以及一个实现接口的类。
At this point, you should have a client class, an interface, and one class that implements the interface.
为了解决这种情况，可以使不同版本的客户端类(包括接口)分隔到不同的包中。
To accommodate this, different versions of client side classes (including the interfaces) may be separated into different packages.
在客户端类中，取消清单26中的以下Accept头媒体类型设置的注释。
In the client class, uncomment the following Accept header media type setting in Listing 26.
除了这两个类之外，必须编写一些绑定代码使GWT可以将客户端类和服务器端类绑定在一起。
In addition to these two classes, you must write some glue code that allows GWT to bind the client-side class and the server-side class together.
因此，对J2EE组件接口（例如EJB 接口）做出很小的改动，就会牵扯到改变大量的客户端类。
Thus, a small change to a J2EE component interface, for example an EJB interface, would cause a ripple effect with changing a multitude of client classes.
现在有一个复杂的工作区，它需要为每个地区创建的客户端类的子类(请参阅参考资料)，但是GWT的工程师正在开发更可行的解决方案。
A complex workaround is available that requires a subclass of each client-side class to be created for each locale (see Resources), but GWT's engineers are working on a more viable solution.
Rabbit MQ客户端类库及后台程序(broker daemon)可一起被用于创建一个AMQP网络，或者单独使用它们以便给建立起来的网络带来RabbitMQ的好处。
The RabbitMQ client libraries and broker daemon can be used together to create an AMQP network, or used individually to bring the benefits of RabbitMQ to established networks.
它的行为将与服务测试相似，不同的是，它将使用服务类为GUI或客户端应用程序提供真正的功能。
It would act like the service tests do, except it would use the service to provide real functionality to a GUI or a client application.
客户端服务层定义了具体的实现类，负责从指示板传递数据、生成请求对象和调用特定的模拟器服务。
The client service layer defines the implementation classes responsible for taking the data passed from the dashboard, creating the request objects, and invoking a specified simulator service.
这就是要使用JAX - RS将类公开给客户端所要做的所有事情。
This is all you have to do to use JAX-RS to expose this class to web clients.
映射主要包括客户端调用的URI和进行处理的动作类。
The mapping primarily consists of the URI called by client and the action class which does the processing.
在客户端，只注册这个新类，不需要注册两个类。
On the client side, you just register the new class instead of both of the classes.
图1显示了各种JAX - WS客户端api之间的类关系。
Figure 1 shows the class relationships between various JAX-WS client APIs.
其中使用绿色框表示客户端，蓝色框表示各种接口和facade类。
A green box is used to represent the client, blue ones to represent various interface and facade classes.
在客户端，定义一个实现 AsyncCallback接口的类。
On the client side, you define a class that implements the interface AsyncCallback.
将PresenceListener实现类和清单6 中所示的类放入客户端WAR。
Place the PresenceListener implementation class and the classes shown in Listing 6 into the client WAR.
这是一种可以使客户端能确定他接收到的是类层次中的什么成员的方法，并相应处理子类中的附加信息。
This is one approach that enables the client to determine what member of the class hierarchy it receives, and process the additional information in the subclass accordingly.
使用客户端截取程序时，客户机截取程序类本身必须处于客户机应用程序的类路径中。
When you use a client-side interceptor, the client interceptor class itself must be in the client application's classpath.
如果您正在加载一个庞大的。NET客户端应用程序或类库，或者硬盘速度很慢，那么这种应用程序的“冷启动”会占用较多的时间。
If you are loading a large.net client application or library, or are using a slow disk, these cold startup scenarios can require many seconds for your application to start.
为运行JMS客户端，样本脚本必须列出针对点到点的类路径条目。
The sample scripts for running the JMS clients must have the classpath items listed for point-to-point.
这主要是因为：服务器端认为实现服务的类是主接口，而客户端则认为服务器端提供的WSDL是主接口。
The basic problem is that, on the server-side, the class implementing the service is deemed the master interface and, on the client-side, the WSDL provided by the server-side is the master interface.
应用推荐