A Process for Supporting Multiple Concurrent Versions of a Remotely Deployed Grid Service
Original Publication Date: 2003-Sep-16
Included in the Prior Art Database: 2003-Sep-16
The article discusses the use of a separate class loader for each remotely deployed web service. This insures that each version of the grid service can load its version of the web service without conflicting with other versions of the web service. Furthermore, since we are not utilizing the classloader associated with the web application, we do not force a reloading of all the classes associated with the web application and thus avoid a restart of the web application which would destroy our long running web services. Next we need to provide solutions to garbage collection of old versions of grid services, routing of clients using generated, static stubs to new versions of a grid service, and distinguishable addressing of each grid service version.