The RMI engine prompts when needed.
RMI引擎在需要时会提示。
If you are using RMI, edit sas.client.props.
如果使用的是RMI，则编辑sas . client . props。
Directly on the service controller via RMI/IIOP
通过RMI/IIOP在服务控制器上直接调用
The currently supported connectors are SOAP and RMI connectors.
当前支持的连接器是SOAP和RMI连接器。
Support for WSIF-invoked internal services, including rmi-iiop.
支持调用WSIF的内部服务，包括RMI - IIOP。
The specification team chose to model JAX-RPC on the existing RMI interface.
该规范团队选择了在现有RMI接口上对JAX-RPC 进行建模。
The name server bootstrap port is also the port for the admin RMI connector.
名称服务器引导程序端口也是adminRMI连接器的端口。
The connector type to use, RMI or SOAP; RMI is recommended as explained below.
欲使用的连接器类型，RMI或soap；根据下面所阐述的，建议使用rmi。
The --port option was not used; thus Geronimo will use the default RMI port of 1099.
没有使用 --port选项；因此Geronimo将使用默认的RMI端口 1099。
The remote region provides a cache region using a remote method invocation (RMI) API.
远程区域提供了一个使用远程方法调用（RMI）API 的缓存区域。
However, you will generally receive notifications faster with RMI than with SOAP.
而一般情况下使用RMI接收通知比使用SOAP更快。
Remote Method Invocation (RMI) employs the serialization process in a special manner.
远程方法调用(Remote Method Invocation,RMI)用特殊的方式利用序列化过程。
T3 was created to work around flaws with the existing RMI implementation provided by Sun.
创建t 3是为了处理Sun提供的现有的RMI实现的缺陷。
Unlike RMI, it is not necessary to generate stub classes and pass them to client machines.
不象rmi，无需生成存根类并将它们传递给客户机。
Method parameters and return values are serialized over RMI-IIOP and returned by value.
方法参数和返回值将在RMI - IIOP上序列化，并由值返回。
I'll examine how RMI differs from SOAP — both SOAP the reality, and SOAP the future promise.
我将研究rmi与SOAP如何不同-包括SOAP的现实和SOAP的未来展望。
Using RMI, you can call methods of remote objects just like you call methods of local objects.
使用rmi，可以像调用本地对象的方法一样调用远程对象的方法。
The decision to use SOAP, RPC, or RMI will have its basis in the programming language you use.
使用SOAP、RPC还是RMI的决定将根据您使用的编程语言。
The J2EE spec stipulates that servlets cannot be RMI servers; they can only be RMI clients.
J2EE规范规定servlet不能是RMI服务器，只能是RMI客户机。
These files specify security configuration to use in RMI-IIOP communication with the server.
这些文件指定了RMI - IIOP与服务器的通信中要使用的安全配置。
You won't have to change your code if you want to switch from JMS to RMI just to name an example.
如果你想从JMS转换为RMI(这只是举一个例子)，你并不用修改你的代码。
This allows remote Method Invocation (RMI) -style remote exceptions to be implemented using SOAP.
这允许使用SOAP来实现RMI风格的远程异常。
The port to connect to (Using the RMI connector: 2809 for Base or 9809 for Network Deployment.
欲连接的端口（使用 RMI连接器：对于基本安装来说是 2809 ，对于网络部署来说则是 9809 。
These other players in your application space probably can't send or receive RMI communication.
您的应用程序空间的其它参与者可能不能发送或接收r mi通信。
Configure the Portal Document Manager connector to use RMI proxy by setting the following parameters.
通过设置以下参数，配置PortalDocumentManager连接器，以使用rmi代理。
You will receive a message like that in figure 15 if your RMI Proxy connector is configured correctly.
如果RMI代理连接器配置成功，您将收到如图15所示的一条消息。
Once again, I'll let you make your own judgments regarding the use of RMI, RPC, and SOAP in your work.
再一次。我让您根据工作中rmi、RPC和SOAP的使用来做出判断。
The best solution is to use RMI to talk directly to stateless session beans in the application server.
最佳解决方案就是使用RMI直接与应用程序服务器中的无状态会话bean对话。
The remote server must also have its RMI port open and its HTTP port open, which is 8080 by default.
远程服务器也必须打开Rmi端口和HTTP端口(默认情况下是8080)。
In general, XML Web Services aren't appropriate for fine grained interactions, even less so than RMI-IIOP.
一般来说，XMLWeb服务对于细小颗粒的交互是不合适的，甚至还赶不上R MI -IIOP。
应用推荐