Tomcat 5.5.20 + BEA Workshop 3.2.1 build 589 issues

Question

Every now and then I run into a problem trying to start my tomcat 5.5.20 instance from within BEA Workshop 3.2.1. I am using the standalone install of Workshop. Repeatedly deleting and adding the server and throwing some restarts of Workshop inbetween seems to provide the voodoo that I need to finally get tomcat starting again from within Workshop...until of course it happens the very next time I stop and restart the tomcat instance or deploy another application to tomcat.
Here is the log entry in my workspaces .metadata\.log file. I hope someone can provide the magic pill that will permanently cure Workshop (and me) of this recurring nightmare!
!ENTRY org.eclipse.core.jobs 4 2 2006-11-19 12:59:19.312
!MESSAGE An internal error occurred during: "Publishing to Tomcat v5.5 @ localhost...".
!STACK 0
java.lang.NoSuchMethodError: org.eclipse.jst.server.core.PublishUtil.deleteDirectory(Ljava/io/File;Lorg/eclipse/core/runtime/IProgressMonitor;)V
     at com.bea.wstudio.debugger.TomcatServerBehaviourBase.publishModule(Unknown Source)
     at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:676)
     at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:756)
     at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:611)
     at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:862)
     at org.eclipse.wst.server.core.internal.Server.publish(Server.java:850)
     at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:142)
     at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)

Answer 1

This is a known issue that occurs for switching application in an existing Tomcat server configuration. The issue has been fixed for the next release (schedule for first week of Dec 06).
Though not elegant the current workaround is as follows:
- Instead of changing the project for debugging on an existing Tomcat configuration, delete and recreate a new Tomcat Server configuration with the new project.
Ex:
In Server view, delete existing Tomcat Server configuration
New > Server, add a new Tomcat server configuration with the new project you plan to debugNOTE: Also, before starting the server make sure to refresh the project in AppXplorer/Package Explorer view so that the resources are insync with the file system.