[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3699) Slow hot deployment - Seam scans and builds component tree each time to check for hot deploy changes

[ https://jira.jboss.org/jira/browse/JBSEAM-3699?page=com.atlassian.jira.pl... ] Vadim Berezniker commented on JBSEAM-3699: ------------------------------------------ I filed bug JBSEAM-4200 earlier today about hot deploy rereading the class files for every request. I started looking into it deeper and I think the problem might have been introduced in the commit for this jira issue. TimestampCheckForwardingDeploymentStrategy calls scan() which calls scan() on the delegate deployment strategy. getScanner() in DeploymentStrategy is never called, which means initScanner() in TimestampCheckForwardingDeploymentStrategy is never used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira