Hi Kevin,
Changes to html, xhtml, jsf, images and other dynamically loaded resources should take effect immediately.
Changes to .class files do not get automatically reloaded by JBoss (for various reasons, mostly related to have Java classloading works and that
if you are testing your application then triggering a reload of application/module will break your running session etc.) .
We know that can be annoying and thus we introduced a "Application reload behavior" in the server section where you can setup a regular expression to
trigger on what files you want a module restart to happen.
In here the default expression is: ".jar$" which means if it sees a file ending with jar be deployed it will trigger an application reload.
But it will not reload if just a single .class is changed.
If you change it to ".jar$|.class$" then it will trigger a restart on every .jar/.class change.
This gives a good balance since then when changing *.xhtml you do not see a forced restart.
of course if you want to be truly agressive you can set the expression to ".*" and you will see restarts of your module on *every* change.