My Develop environment is tomcat 5.5, jdk 1.5 and eclipse 3.1 using sysdeo plugin for tomcat. When I start the server the default tomcat web application manager window is showing all the applications which are hosted on the server. But this list is still showing the aplications which I have removed from the package explorer in the eclipse IDE. How to make this deleted applications not to be listed in the tomcat web application mager window.
Hello Jeanne, The Running option shows " true " for the deleted applications also. I dont understand this, why the deleted applications are also get listed in web application manager window.Due to them while starting the tomcat the console showing errors related to those applications. So I explicitly making them Undeployed by clicking the Undeploy option in the command option. So, How to make them deleted permanatly as not to be shown in web application manager window.
[ February 23, 2007: Message edited by: vijay kumarg ] [ February 25, 2007: Message edited by: vijay kumarg ]
There's 2 ways of being "deployed". The unimportant one is whether or not the sysdeo plugin thinks a project is a Tomcat project. That merely means that the source code is visible to the plugin and is eleigible for breakpoints. I use that for such non-webapp things as debugging Tomcat security realm modules.
sysdeo is not an appserver in its own right, however, just a means of integrating Tomcat into the Eclipse editing and debugging environment. So to truly undeploy an app, you have to undeploy it from Tomcat itself.
In tomcat5, stop Tomcat, delete the application from TOMCAT_HOME/webapps. Both the exploded WAR and the unexploded WAR, if present. If you deployed using a context deployment, delete the context file from TOMCAT_HOME/conf/Catalina/localhost.
An alternative is to use the tomcat management webapp. Start up Tomcat, and invoke the manager webapp Or the admin webapp. I can never remember which does which. In either event, these apps are both protected with userids and passwords, so you need to have an account with appropriate security roles in order to sign in and use them, One or the other has an "undeploy" operation that will automatically do what I described up above, though without the trauma of shutting the rest of the Tomcat server down first.
BTW, the admin app in the Tomcat 5.0.30 release was broken, so they did a separate release of just that one app, properly repaired. I prefer 5.0.28, however, which doesn't have that problem. Or more recently, a 5.5 Tomcat.
Customer surveys are for companies who didn't pay proper attention to begin with.