[ https://jira.jboss.org/jira/browse/JBSEAM-3699?page=com.atlassian.jira.pl... ] Dan Allen updated JBSEAM-3699: ------------------------------ JBoss Forum Reference: http://seamframework.org/Community/HotDeploymentIsSlowAndHasBugsWithSeam21 -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-3699?page=com.atlassian.jira.pl... ] Dan Allen commented on JBSEAM-3699: ----------------------------------- I did major cleanups in the process of fixing this issue. The good news is, hot deployment is no longer negatively affecting the performance of the application (though you still don't want to be using it in production). For an application with ~300 hot deployable components and ~600 web resources, a request having no source code updates went from 2s to 0.07s. A redeployment dropped from 13s to 4.5s. Here's what got fixed: - warTimestamp wasn't being set, so the WarRootDeploymentStrategy scan (for .page.xml files) was happening on every request - DotPageDotXmlDeploymentHandler was being used in HotDeploymentStrategy, but it only belongs in WarRootDeploymentStrategy; this caused unnecessary processing for each scanned file - only update the timestamp of the scan if the file is actually handled by the scanner (preventing redeployment when an unrelated file changes, such as .xhtml) - add excludedDirectories to Scanner#scanDirectories to avoid decending into select directories; this speeds up the scanning of the WAR root tremendously - set of hot deployable component names where not being cleared before installing the news ones - introduce a wrapper strategy (actually one for HotDeploymentStrategy and one for WarRootDeploymentStrategy) that run a scanner that only checks the timestamp and does not other processing; that is equivalent to the simple timestamp check from Seam 2.0 except that it is sensitive to the filtering the strategy's deployment handlers provide - the org.jboss.seam.hot.hotDeployFilter should be configured with a urlPattern that matches the JSF servlet! I need to update the docs, but for now I added this to seam-gen projects for reference - did some general refactoring around the init and redeploy routines to make small optimizations here and there -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-3699?page=com.atlassian.jira.pl... ] Pete Muir commented on JBSEAM-3699: ----------------------------------- It also looks the are now some bugs in redeploy() -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-3699?page=com.atlassian.jira.pl... ] Ciro Cavani commented on JBSEAM-3699: ------------------------------------- I am using hot deployment and Groovy to enable script extension on my intranet application. Something like a simple modular system for non-programmers on top of Seam/Java application for data management. Some issues you may have touched: More customizable hot redeployment https://jira.jboss.org/jira/browse/JBSEAM-1634 Debug/development mode control https://jira.jboss.org/jira/browse/JBSEAM-3159 WEB-INF/dev should be processed even if not in debug mode https://jira.jboss.org/jira/browse/JBSEAM-1172 And the one I would really want: Allow customization of WEB-INF/dev/ location https://jira.jboss.org/jira/browse/JBSEAM-2496 (and I suggest more than one directory configurable) Thanks, -- 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

[ 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