|Here are the ways you can get a Servlet Class file that is currently loaded in the JVM to be replaced with a newer version of Class file without having to restart anything:
If you use JSPs, SE will always use the most current version of the JSP that is being requested.
If your servlet resides in the folder designated as the "Servlets" folder for that ServletExec Virtual Server then the newest version of its Class file would be picked up automatically and used by ServletExec the next time that Servlet was requested. This includes a servlet that is in a JAR or ZIP archive having the same name as the servlet
If your servlet is part of a Web Application (WEB-INF folder, web.xml file, etc...) then you could manually reload the entire web application from the main SE admin UI (SE 3.x or higher).
If your servlet is Configured (on the main ServletExec Admin UI)
AND it is either a Remote Servlet or a Servlet that resides in the designated "Servlets" folder then you could manually Reload it from that admin page in order to get the newest version of the Class file to replace the older one that is still in the JVM.
Note: For a Configured servlet whose class file does NOT reside in the designated Servlets folder and is NOT remote, reloading it from the Manage Servlets page of the main SE admin UI does NOT cause its class file to be reloaded into the JVM.
It DOES cause that Servlet's destroy() method to be called, and a new Servlet instance is then created from the originally loaded class file. The init() method is then called on that new Servlet instance.