We have recently moved our product to work on top of the J2EE platform. One question I have is in regards to multiple application servers. We have written our application to the J2EE specification , in order to run across various AppServers. Some of our customers do have AppServers from multiple vendors (Weblogic, Websphere, etc...). There are two situation in which this becomes problematic if our customer has decided to install more than one instance of our product on different Application Servers.
1. Our fat clients that connect to the AppServer need client libraries for each different AppServer they need to connect to. 2. Our application also involves cross-communication between instances. Instance A of our product (running on Weblogic) will create a Process on instance B of our product (running on JBoss) through a Stateless Session Bean. I believe that both of these situations should work if we included all of the Application Server's specific client libraries with our client and server applications. It just seems to be quite a bit of maintenance to keep these libraries up to date. Is there a better way to deal with this that any one has implemented? Is Using Web Services for cross-instance communication the best alternative? Has anyone had versioning issues when dealing multiple versions of the same AppServer vendor? Any Help appreciated! Shone Sadler Q-Link Technologies http://www.qlinktech.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".
