Java™ Application Development on Linux - Dator

22.2 EJBs: You Don’t Know Beans?497public Costdebt(double amt, double rate, double paymnt)throws java.rmi.RemoteException{return SAMoney.debt(amt, rate, paymnt);} // debtpublic voidsetSessionContext(SessionContext context){sessionContext = context;} // setSessionContextpublic voidejbCreate() { }public voidejbRemove() { }public voidejbActivate() { }public voidejbPassivate() { }} // interface MoneyEJBean22.2.2 EJBObjectAt the other end of the chain of EJB objects used to accomplish all this distributedcomputing is the object that our application is actually going to touch.When our application creates an EJB, it, acting as a client, won’t actually getits hands on the distant session (or entity) bean because that session bean isrunning somewhere out in the network. There will be, however, a proxy object,acting on behalf of the distant EJB. It is described as the remote interface, becauseit is remote from the EJB (though very close to the application). It is aninterface because J2EE supplies a class that does the hidden work of marshalingthe data, contacting the EJB, sending the data and receiving the results; theapplication developer only adds a few additional application-specific methods,via this interface (Example 22.2).