rmi

Java RMI 指的是远程方法调用 (Remote Method Invocation)。它是一种机制，能够让在某个 Java 虚拟机上的对象调用另一个Java 虚拟机中的对象上的方法。可以用此方法调用的任何对象必须实现该远程接口。 Java RMI不是什么新技术（在Java1.1的时代都有了），但却是是非常重要的底层技术。 大名鼎鼎的EJB都是建立在rmi基础之上的，现在还有一些开源的远程调用组件，其底层技术也是rmi。 在大力鼓吹Web Service、SOA的时代，是不是每个应用都应该选用笨拙的Web Service组件来实现，通过对比测试后，RMI是最简单的，在一些小的应用中是最合适的。 下面通过一个简单的例子来说明RMI的原理和应用，下面这个例子是一个简单HelloWorld，但已涵盖RMI的核心应用与开发模式。 package com.jason.rmi; import java.rmi.Remote; import java.rmi.RemoteException; public interface Hello extends Remote{ public String sayHello() throws RemoteException; public String sayHelloToSomeOne(String someOneName) throws

Java RMI 指的是远程方法调用 (Remote Method Invocation)。它是一种机制，能够让在某个 Java 虚拟机上的对象调用另一个 Java 虚拟机中的对象上的方法。可以用此方法调用的任何对象必须实现该远程接口。 Java RMI不是什么新技术（在Java1.1的时代都有了），但却是是非常重要的底层技术。 大名鼎鼎的EJB都是建立在rmi基础之上的，现在还有一些开源的远程调用组件，其底层技术也是rmi。 在大力鼓吹Web Service、SOA的时代，是不是每个应用都应该选用笨拙的Web Service组件来实现，通过对比测试后，RMI是最简单的，在一些小的应用中是最合适的。 运行RMI服务端程序： 运行RMI客户端程序： 总结： 从上面的过程来看，RMI对服务器的IP地址和端口依赖很紧密，但是在开发的时候不知道将来的服务器IP和端口如何，但是客户端程序依赖这个IP和端口。 这也是RMI的局限性之一。这个问题有两种解决途径：一是通过DNS来解决，二是通过封装将IP暴露到程序代码之外。 RMI的局限性之二是RMI是Java语言的远程调用，两端的程序语言必须是Java实现，对于不同语言间的通讯可以考虑用Web Service或者公用对象请求代理体系（CORBA）来实现。 下面通过一个简单的例子来说明RMI的原理和应用，下面这个例子是一个简单HelloWorld

I'm working on Java RMI application, and having problem binding a server to the registry. I'm working on eclipse using rmi plugin, and everything worked fine before I had to format my pc. Also, I'm sure the code is ok since it's the one given to me as a solution, so there must be something wrong with my configuration. Here's the code: public static void main (String[] args){ try{ RMIChatServer myObject = new RMIChatServerImpl(); System.setSecurityManager(new RMISecurityManager()); Naming.rebind("Hello", myObject); System.out.println("Remote object bound to registry"); } catch( Exception e){

Is communication between clients and servers in java rmi secure (i.e. encrypted by default)? Encoded, yes. Encrypted, no. JERI for JINI gives JRMP (the RMI protocol) over SSL, IIRC. JSR #76 would have provided RMI Security, however it was controversially voted down . I think you mean "encrypted" not "encoded". The answer is no. If you're using RMI in a non-trusted environment I would suggest something like RMI over SSH tunneling . By secure I guess you mean encrypted. Not by default with RMI. You can use custom socket factories to encrypt RMI comms. In short, no. http://java.sun.com/j2se/1.4.2

If i want to enable 'two way' communication in my RMI Application (That is, allow the server to invoke methods on the client, as well as the client to invoke methods on the server), is the simplest way to make the client into a Remote class as well? Also if i intend to pass instances of my client to server as a method parameter, am i correct in thinking that there is no need to add the 'client class' to the rmiregistry? And one final question, do all of my classes still need to be compiled in the same place? I.E can i compile server and client on two entirely independent machines and expect

When I implement an RMI server (implement an interface that extends java.rmi.Remote) is there a way to get information about the current RMI request context, specifically the remote client's IP address? public void myMethod() throws RemoteException { log.info("remote IP is "+ RMISomething.getSomething()); } See java.rmi.server.RemoteServer#getClientHost 来源： https://stackoverflow.com/questions/590257/determine-remote-client-ip-address-for-java-rmi-call