[seam-issues] [JBoss JIRA] (JBSEAM-4869) Components at Application Scope in Glassfish v2 not being destroyed

Components at Application Scope in Glassfish v2 not being destroyed ------------------------------------------------------------------- Key: JBSEAM-4869 URL: https://issues.jboss.org/browse/JBSEAM-4869 Project: Seam 2 Issue Type: Bug Components: Core, Platform interoperability Affects Versions: 2.2.2.Final Environment: Glassfish v2.1 and Tomcat 5.5.9 Any OS Reporter: Jose Pedro Pereira Labels: Destroy, Lifecycle, SeamListener, glassfish Original Estimate: 2 days Remaining Estimate: 2 days The Tomcat 5.5.9 had a bug concerning the calling of the contextDestroyed callback method on a ServletContextListener so that the ServletContext attributes map was cleared before the Listener was called. This means that the SeamListener class is not able to destroy components at ApplicationContext scope, because the ServletContext no longer has a reference to those components. Although it seems to be an error which has been fixed in Tomcat6, wouldn't the solution be cleaner in Seam if Seam just binds as an ServletContextAttributeListener, so that it can allways be informed whenever the WebContainer "feels like" clearing an attribute? Wouldn't this solution be stronger? I'll gladly contribute such code if the response is positive...