Hi > 2. If the application scale up to cluster, this design seems can't deal with it > (because the client always invoke remote object that was downloaded to > cache, which is not dynamically locate by app. server in a cluster > environment.)
Is this really an issue? Maybe I do not understand you correctly. Is this the scenario you are thinking of: When plugin is initialized it uses J2EE Server A to get the remote object. Meantime J2EE Server A breaks down. Do you mean that remote object would not be accessible anylonger? I do not think this is an issue. It mmust be up to the J2EE Server to "hide" clustering from the clients (here the plugin class) I can see an issue in clustering though..The J2EE server must be able to share/distribute ServletContexts across clusters...but isn't that a part of the J2EE specs? Any thoughts...also from others... Regards Henrik --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
