The problem with JBoss hot deployment today is that redeployment occurs when something changes. Which means that if you are editing stuff in eclipse, and the seam-gen build is copying that stuff across to the deploy dir, you have two choices: (1) touch the descriptor every time, and get thousands of redeploys (JBoss blows up when it runs out of permgen space) (2) don't touch the descriptor until user explicitly asks for a restart (which is irritating to user) The way Seam's hotdeploy works is that it redeploys the components when a request comes in, and it notices that there has been some change in WEB-INF/dev. Which means that you avoid the permgen errors. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025903#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...