I have another recommendation unless the first recommendation is welcomed. There could be some time checks between redeployments. Some seconds before doing the successive redeployment. It is not probable??? for someone to do two consecutive redeployments for some?? seconds.
Change a file in your ide. Go to your browser and request a page. Then go to your ide again. Change something and save. And browse a page.
Your changes are deployed when you hit your application!
Ramazan YILDIRIM wrote on Oct 26, 2008 22:21:
The problem with hot deployment is for each request, Seam does scan all the class files for a change checking their last modifed time. While doing this it does also generate the component tree. And this component tree generation takes long long time.
Please file an issue for this in JIRA.
Secondly, Seam redeploys war directory content on each request. Actually it even doesn't check if there is a change!
Pleae report this in JIRA.
Second thing is I applied an exclusion filter for xhtml files. They are excluded from scans. Mostly changes are done to xhtml files and they have nothing got to do with seam.
Please report this in JIRA.
Oh and there is a bug in URLScanner.handleScanner method it actually should be touchTimestamp(child); but it is touchTimestamp(file);
It keeps checking the parent directory for each file.
Pleae report in JIRA
What I would suggest you do is create a seperate issue for each of the above, and link them together. Please also file a feature request for your suggestion about a delay between redeploys.
Thanks for looking into this, I made a bad assumption about how long it takes to process the deployed files.
I got this problem too, with debug true my pages are 50 sec slower, and with debug false its working perfect.
Thanks for debugging this! I've had the same problem - development mode was completely unusable. For the time being, I just added back the file timestamp check from 2.0.2 to org.jboss.seam.debug.hot.HotDeployFilter in jboss-seam.debug.jar. This makes things usable again.
What do you mean with
debug true? Do you mean to start the server in debug mode, or to a xml file property anywhere?
I guess it´s the debug property in components.properties ;-)