Hot deployment scanner deploys files which were expected to be filtered ----------------------------------------------------------------------- Key: JBAS-5209 URL: http://jira.jboss.com/jira/browse/JBAS-5209 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.Beta3 Environment: JBoss-5.0 Beta3, Sun Java 1.5, Windows 2003 Reporter: jaikiran pai The hot deployment scanner org.jboss.system.server.profileservice.hotdeploy.HDScanner while scanning for any modified/removed/added applications, picks up files which are meant to be filtered out. Here's the scenario: - Create a valid EAR file (ex: myApp.ear) - Place this file in the deploy folder of the server and rename it to myApp.ear.bak (so that it is filtered out from deployment) - Start the server. - Server starts fine and as expected the myApp.ear.bak is not deployed as it is filtered out by the VFSDeploymentScannerImpl using the ExtensibleFilter. - However, once the server has started and the next run of HDScanner starts, the HDScanner adds the myApp.ear.bak to a list of "new" applications to be deployed. Because of which the myApp.ear.bak gets deployed (which is not what we wanted). The reason appears to be because HDScanner isn't filter aware. As a result the getModifiedDeployments() method on the ProfileImpl adds this .bak file to the list of new applications to be deployed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira