Seam scans the WEB-INF/dev classpath for hot redeployment. To avoid this, simply use debug=
Thanks Adrian! If I do that, then the application must be restarted for every change. If possible I'd like to have hot deployment enabled during development.
I was hoping to hear from people who use debug/hot deployment during development about how fast it works for them.
If they say that they notice a small performance difference, clearly I'm doing something wrong and I should attempt to figure out whether I'm using the wrong JRE, version of JBoss, have two many components, etc....
JBoss scans the server/xxx/deploy directory for hot deployment of EAR, WAR and foo-ds.xml files. IIRC you can tweak the interval for the scan (default <= 5000ms IIRC).
So perhaps you can tweak this setting as well if it is available in the Seam config/API.