[ http://issues.apache.org/jira/browse/MYFACES-730?page=comments#action_12355674 ]
Steve Peterson commented on MYFACES-730: ---------------------------------------- Is code review really the only way to get to this? I'd be willing to help but don't know where to start. I just tried to run it down by expanding the jar into the WEB-INF/classes but, of course, the webapp cleanly deploys in that situation. Note that the problem occurs during initialization; the jar is open at the point that the webapp is initialized, but before the first request is processed. http://tomcat.apache.org/faq/windows.html#lock has some notes on what might cause the problem. > 1.1.1RC3 jar interferes with Tomcat undeploy > -------------------------------------------- > > Key: MYFACES-730 > URL: http://issues.apache.org/jira/browse/MYFACES-730 > Project: MyFaces > Type: Bug > Components: General > Versions: 1.1.1 > Environment: XP SP 2, Tomcat 5.0.28, JDK 1.4.2_08 > Reporter: Steve Peterson > > Did a test upgrade of a MyFaces 1.1.0 based app to 1.1.1 RC3. The app is > deployed in Tomcat 5.0.28. > After the application is deployed and I use it for a little bit, I try to > undeploy it. The undeploy fails because the myfaces-all.jar file is still > open after the application is stopped. The only workaround is to stop Tomcat > and restart it. > The 1.1.0 myfaces-all.jar file did not exhibit this behavior. > My experience is that this occurs if there is an open reference to a resource > in the jar file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
