I believe this is only an issue for Application scope services, because Apache SOAP keeps the single instance in memory. If for example you were working with Request level services, the instance would be deleted each time.
For application scope stuff I do the same as you, I stop and restart Tomcat. -----Original Message----- From: fmeredith [mailto:[EMAIL PROTECTED]] Sent: Monday, October 15, 2001 12:10 PM To: [EMAIL PROTECTED] Subject: Restarting Tomcat I've noticed that every time I re-compile a Java class that is used on the server side of a SOAP transaction, I've had to restart Tomcat in order for the changes to take effect. Is this behavior common with other users out there? And is there a configuration setting that will allow me to avoid that restart process? Tomcat version 3.2.2 Any help is greatly appreciated,
