Java™ Application Development on Linux - Dator

5.8 Introducing RMI147Example 5.14 Compiling and running our server on penfold.penfold$ javac net/multitool/RMIDemo/SessionImpl.javapenfold$ rmic net.multitool.RMIDemo.SessionImplpenfold$ rmiregistry &17286penfold$ java net.multitool.RMIDemo.SessionImplAsked to add 47 and 135.8.4.4 Compiling and Running the ClientExample 5.15 shows the actual steps we ran to build and run the client.Example 5.15 Compiling and running our client on grovelgrovel$ javac net/multitool/RMIDemo/Client.javagrovel$ javac net/multitool/RMIDemo/SessionImpl.javagrovel$ /usr/java/jdk/bin/rmic net.multitool.RMIDemo.SessionImplgrovel$ java net.multitool.RMIDemo.ClientPointless RMI Client. 47+13=60, right?grovel$NOTEWe compile the server class, SessionImpl, on the client side and run rmicagainst it just to produce the stubs the client requires. You could copy the stubclasses from the server machine, or you could put them in a JAR file, put that fileon a Web server, and have the java.rmi.server.codebase property pointto that JAR file. We’re taking the simple way here, but in a real implementation,you would not do it this way. We’ll cover more realistic cases later.5.8.5 RMI SummaryRMI greatly simplifies the business of writing multitier client-server applications.It is suitable for many classes of distributed computing problems, but itdoes lack several features that required in large, mission-critical applications.For one thing, it lacks any sort of transaction support. If a method invocationfails, the client may not know for certain whether the server finished some work,like writing to a database, before the failure. Also, the rmiregistry program is