You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Matthias Weßendorf (JIRA)" <de...@myfaces.apache.org> on 2006/08/26 09:08:24 UTC
[jira] Commented: (MYFACES-730) 1.1.1RC3 jar interferes with Tomcat
undeploy
[ http://issues.apache.org/jira/browse/MYFACES-730?page=comments#action_12430709 ]
Matthias Weßendorf commented on MYFACES-730:
--------------------------------------------
what's with newer versions?
(nothing tested here from my side)
> 1.1.1RC3 jar interferes with Tomcat undeploy
> --------------------------------------------
>
> Key: MYFACES-730
> URL: http://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.
-
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