rmi

rmi

美 　英

• 网络远程方法调用(Remote Method Invocation)；远程方法调用(Remote Method Invoke)；成熟指数

例句

Knowing that this RMI replacement exists is often enough (detailed understanding of T3 is not required to be effective in a migration role).

知道RMI的这个替代品存在通常就够了（在迁移角色中，对T3的详细理解是不需要的）。

From there, I'll go on to compare SOAP, and RPC in general, with one of its biggest competitors, remote method invocation (RMI).

从那里，我继续将SOAP和一般而言的RPC与它的最大竞争对手之一，远程方法调用（RMI）相比较。

which will cause the RMI registry to be started in its own DOS window. The RMI registry must be started before you can start your server.

这将会使RMI注册器在它自己的DOS窗口下运行.RMI注册器必须在你运行你自己的服务器之前运行。

In practice, it's mostly Java programmers who are using SOAP anyway, so it's back to the original question of whether to use RPC or RMI.

实际上，使用SOAP的大多数是Java程序员，所以又回到了原来的问题，使用RPC还是使用RMI。

Messages can be sent to a destination using SOAP over HTTP, or MQ or RMI over IIOP, just to name some of the possibilities.

使用HTTP上的SOAP可以将消息发送到目的地，或是使用IIOP上的MQ或RMI，只是命名一些可能性。

Java already had an existing technology for RPC calls between Java applications, in the form of RMI (Remote Method Invocation).

Java当时已经有了一项面向Java应用程序间的RPC调用的现有技术，即远程方法调用（RemoteMethodInvocation，RMI）。

The RMI house has two solar panels that are designed to follow the sun throughout the day.

此外，马绍尔的房子有两个旨在遵循在一天内太阳太阳能电池板。

The beauty here is being able to capture join points without additional collaboration beyond that required by the RMI infrastructure.

这里很好的一点是可以不需要加入比RMI基础设施所需要的更多的协作就可以捕获连接点。

This encoding process is called marshalling, and it is an important element of the Java RMI Specification.

这个编码过程叫做编组（marshalling），它是JavaRMI规范的重要元素。

API. It includes an RMI proxy and a daemon application, which allow Java applications to access USB devices on a remote computer.

它包括一个RMIproxy和一个daemon应用程序，它让Java应用程序可以访问远程计算机上的USB设备。

To see the actual difference in times, you can run the sample code with both the SOAP and RMI connector and compare the results.

要想看时间上的实际差别，您可以分别使用SOAP和RMI连接器来运行样本代码，然后比较结果。

It is the foundation on which the EJB container depends to broker communication for Java Remote Method Invocation (RMI) interactions.

它是EJB容器赖以进行代理通信的基础，以便实现Java远程方法调用（JavaRemoteMethodInvocation，RMI）交互。

Most of the hot water in the RMI house comes as a result of these heating panels.

在热水中的大部分RMI的房子里来，由于这些加热板的结果。

The best solution is to use RMI to talk directly to stateless session beans in the application server.

最佳解决方案就是使用RMI直接与应用程序服务器中的无状态会话bean对话。

The target server invokes the login modules from the RMI_INBOUND login configuration to pick up the credentials from the incoming request.

目标服务器调用RMI_INBOUND登录配置中的登录模块，以便从传入的请求获得凭据。

It might be called from a JMX listener, an action listener in the GUI event thread, through RMI, through a Web service, and so on.

（可能会从JMX侦听程序、GUI事件线程中的操作侦听程序、通过RMI、通过一个Web服务等调用）。

In the following section, I discuss the major factors necessary to making a choice among the three options: SOAP, RPC, or RMI.

在以下的章节中，讨论了在这三种选项：SOAP、RPC或RMI之间作出选择所必需的主要因素。

Here I'll compare SOAP to its biggest competitor for communication in the Java space, RMI (remote method invocation).

这里，我将SOAP与Java空间中通信方面，它最大的竞争对手RMI（远程方法调用）进行比较。

The RMI specification specifies a marshalling algorithm, which is applied to the serialized form of Java objects.

RMI规范指定编组算法，并把算法应用到Java对象的序列化形式上。

RMI and CORBA are often seen as competing technologies, since both provide transparent access to remotely distributed objects.

RMI和CORBA常被视为相互竞争的技术，因为两者都提供对远程分布式对象的透明访问。

In determining whether to use RMI over RPC or vice versa, it's important to look at the means of interaction the two employ.

在决定是否用RMI而不用RPC或者反之亦然时，看一下这两者采用的交互方式是重要的。

The evolution and deduction of function can be done through connection, mapping and inversion, which is called RMI Principle.

函数的关系演变推导，可以用关系、映射、反演方法解决，这种方法就叫做“RMI”原则方法。

This environment (specifically JBoss) supports the propagation of a client transaction across multiple JVMs (using RMI-IIOP).

这种环境（特别是JBoss）支持跨多个JVM传播客户端事务（使用RMI-IIOP）。

This allows Remote Method Invocation (RMI)-style remote exceptions to be implemented using SOAP.

这允许使用SOAP来实现RMI风格的远程异常。

It provides a simple way for service providers to describe the format of requests and response messages for remote method invocations (RMI).

它为服务提供者提供一个简单的方法描述申请的形式并响应远程方法调用信息（RMI）。

Unlike the RMI example, nothing inherent in an element's name or signature suggests transactionality or authorization characteristics.

与RMI的例子不同，在元素名或者签名中没有什么内在的东西说明事务性或者授权特性。

The RMI framework then manages communication with the remote object, which results in remote invocation of the required methods.

然后RMI框架管理与远程对象的通信，形成对所需方法的远程调用。

And, of course, RMI transport involves the serialization of Java objects.

当然，RMI传输还涉及Java对象的序列化。

Does not support Java Native Interface (JNI), Raw Native Interface (RNI), and Remote Method Invocation (RMI).

不支持Java本机接口（JNI）、原始本机接口（RNI）和远程方法调用（RMI）。

But there is certainly more to SOAP than just messaging, and I'll now show how clients interact with SOAP, and how they interact with RMI.

当然，SOAP不仅仅是消息传递还有更多，现在，我将演示客户机如何与SOAP交互，以及如何与RMI交互。

In the server settings, make sure that you have SOAP enabled (not RMI) for the server connection type, as shown in Figure 15.

在服务器设置中，确保为服务器连接类型启用了SOAP（而不是RMI），如图15所示。

Description: This sample will guide you through the steps to create a simple RMI application.

描述：这个示例将会教你建立一个简单的RMI应用程序的步骤。

All of our remote POJO implementations are exposed to the external world via SOAP, RMI, and our custom tunneling classes.

通过SOAP，RMI，以及我们客户化的隧道类等途径，所有的远程POJO实现都向外开放。

The information release in enterprise is solved by the blue print of the application server using RMI.

基于RMI技术构建的应用服务器为企业信息发布提供了解决方案。

Remote Method Invocation (RMI) employs the serialization process in a special manner.

远程方法调用（RemoteMethodInvocation，RMI）用特殊的方式利用序列化过程。

The name server bootstrap port is also the port for the admin RMI connector.

名称服务器引导程序端口也是adminRMI连接器的端口。

From there, it would be best to have the client establish a direct RMI connection with one or more session beans.

然后，最好使客户机与一个或多个会话bean建立直接的RMI连接。

Messages can be transferred via web services, REST, EJBs, RMI, HTTP, Sockets, SSL or any similar communication interface.

消息可以通过Web服务、REST、EJBs、RMI、HTTP、Sockets、SSL或任何类似的通信接口进行传输。

The target server receives the incoming request and starts invoking the login modules from the RMI_INBOUND login configuration.

目标服务器接收传入的请求，并开始调用RMI_INBOUND登录配置中的登录模块。

Unlike RMI, it is not necessary to generate stub classes and pass them to client machines.

不象RMI，无需生成存根类并将它们传递给客户机。