In your case, there is no advantage to using RMI lookup. The RMI lookup routines where added to Java before JNDI existed, otherwise we wouldn't have them at all. In today's world, we use the RMI lookup only when one doesn't have JNDI available (such as when not using an application server). In the case of EJB, JNDI is central to the architecture, and in many application servers you can't avoid it's use (because the smart stubs are JNDI aware). If your customer wants you to use RMI lookup with EJB, it'll be your job to convince them this isn't the architecture they want to use. In short, let RMI do RMI's job of remote procedure calling, and let JNDI do JNDI's job of looking up services over a network.
Doug =========================================================================== 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".
