[
https://issues.apache.org/jira/browse/MYFACES-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558662#action_12558662
]
Simon Kitching commented on MYFACES-730:
----------------------------------------
Any feedback on this? If not, this should be closed as it is a
hard-to-reproduce bug (only on original poster's machine) and is now 1.5 years
old with no additional info.
> 1.1.1RC3 jar interferes with Tomcat undeploy
> --------------------------------------------
>
> Key: MYFACES-730
> URL: https://issues.apache.org/jira/browse/MYFACES-730
> Project: MyFaces Core
> Issue Type: Bug
> Components: General
> Affects 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.
-
You can reply to this email to add a comment to the issue online.
