Thank you for the suggestions. We were not cleaning up properly the temporary folder where we create our WAR file, so that old CXF file was there for this reason but was not the cause of the problem. In fact, the problem still exists with the other file (cxf-2.1.2.jar), which still prevents Tomcat from completely undeploying the web app.
We have found on (http://wiki.metawerx.net/wiki/TroubleshootingApplicationDeploymentOnTomcat) a reference to an antiJARLocking="true" to be set in the Context (ie: in the context.xml file or server.xml file) during development. We'll try this out and then report. Any other hint would be much appreciated. dkulp wrote: > > > First question: > >> cxf-2.0.5-incubator >> cxf-2.1.2 > > Why is there two versions of cxf there? That's definitely asking for > problems. > > Dan > -- View this message in context: http://www.nabble.com/Problem-undeploying-a-web-app-using-CXF-2.1.2-from-Tomcat-6-tp19632733p19646841.html Sent from the cxf-user mailing list archive at Nabble.com.
