Hello Dejan referencing the manager capabilities from tomcat located at http://tomcat.apache.org/tomcat-5.5-doc/manager-howto.html#Undeploy%20an%20Existing%20Application
to undeploy AxisServlet (which is originally deployed as webapp labeled axis one must specify path=/axis) as in this example http://localhost:8080/manager/undeploy?path=/axis Martin -- --------------------------------------------------------------------------- This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. --------------------------------------------------------------------------- Le présent message électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire. ----- Original Message ----- From: Dejan Milošević To: [email protected] Sent: Monday, December 25, 2006 10:01 AM Subject: RE: jars locked forever Hello Martin, I don’t know about other app servers, but for WebSphere there are obvious options ’update application’, ’uninstall’, ’install’, ’start’, ’stop’ which I use often for other web apps and would like to use for the app that’s holding my web services (axis2 app). So the answer is: jars should be reloaded when application is restarted (next level could be ’when application is reinstalled’, and even that doesn’t work (next_next level ’when app server is restarted’ works, but that’s almost as bad as ’when windows is restarted’ J )). One thought: how can one JUST UNINSTALL this phantom axis servlet without stopping the entire servlet container? ------------------------------------------------------------------------------ From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Monday, December 25, 2006 3:27 PM To: [email protected] Subject: Re: jars locked forever Good Morning Dejan If the jars were unlocked (and updateable) when would these (updated) jars for AxisServlet (or any servlet) be re-loaded or re-deployed? Martin -- --------------------------------------------------------------------------- This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. --------------------------------------------------------------------------- Le présent message électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire. ----- Original Message ----- From: Dejan Milošević To: [email protected] Sent: Monday, December 25, 2006 9:00 AM Subject: jars locked forever Once axis2 servlet is started in a servlet container it locks all the jars that are in the WEB-INF/lib folder of the webapp that contains the axis2. These locks are not released until the whole application server is stopped. I have problem with this, since I use some common jars for many services, and these jars need to be updated sometimes (so I put them in WEB-INF/lib), but I don’t want to restart the whole server (which is serving other apps as well) just because of these jars! Is this a bug? Any solutions?
