Lam: > This is a great news! However, when I use j2ee deployment tool to deploy a > bean, I cannot deploy it to multiple hosts. That means, if I use one client jar > file for the remote interface, it will connect to only the host I deploy the > bean. I may be wrong; I haven't proved it yet. I haven't used the J2EE reference server yet, so I can't help you with that. > If I can deploy a bean to multiple hosts and obtain one jar file for remote > client, I'll be very happy. Do you know which commercial EJB server does this? > or how to configure it? Our product, GemStone/J, will do this for you. In fact, if all of the server machines have access to a common file system, you only have to deploy the server components once, and other machines can get them either from the file system or from our distributed shared object cache. The client, meanwhile, needs only one jar, which contains information that allows the client to connect to our JNDI name service and our EJB activator, both of which transparently distribute requests to the various machines in your configuration. There's more information at www.gemstone.com. Also, if you tell me where you're located, I can refer you to one of our sales agents, who can answer a lot more questions. Marc San Soucie GemStone Systems, Inc. Beaverton, Oregon [EMAIL PROTECTED]
