>>>My question is : >>>Do we need to keep the stub in client machine(Copy the stub from ejb >>>server and put in client's runtime classpath) ? If yes why? Yes, because EJB remote client communication is based upon Java RMI (and now RMI over IIOP) and that is how Java RMI works so that you can automagically call an object in another JVM process.
>>>Is it not that the stub will be automatically downloaded to client >>>machine when first time client calls ejb ? RMI does have dynamic code downloading, but it is not part of the J2EE/EJB spec. You may be able to build something like this, but it is not a standard operation of the appserver. I don't know of anything like this for EJBs on WebSphere. You will need the classes to build the client as a minimum. >>>What other classes required in client side ? All classes for any reference types that your EJB methods take or return. Appserver specific classes such as ejs.jar and ujc.jar for WebSphere 3.5. There are also typically JDK version dependencies between what the EJB remote client and server are running. Assuming you are running the same version of WebSphere in both places you will only need to worry about the client related classes. >>>Is this App server specific ? (is that For only some app server we need >>>to do this manually). Not where they follow the EJB spec in regards of what the required EJB remote client classes are. The appserver specific jars are though. >>>Any Pointer to above question will be greatly appreciated. Hope this helps. >>>Thanks, >>>Subhendu -Chris Thompson Bean-test Developer http://www.empirix.com =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
