Hot deployment is cool, but there is a risk of:

1. Class-Loader exceptions (more on this later)
2. Unrecognized configuration settings
3. Lost session/application scoped data

Cold deployment is slow but stable

1. Stop JBoss AS
2. Optionally delete data/, log/, tmp/, work/
3. Redeploy your application(s)
4. Start JBoss AS

Learn the core features of JBOSS Traning and become master with our expertise tutorials.

Hot deployment is generally considered safe for:

1. Java Server Pages (.jsp) files. They get recompiled automatically by the servlet engine following a change.
2. Class files that do not change their public interfaces, especially when there is no RMI involved. This requires full redeployment, so it is still somewhat risky.

For indepth understanding on JBoss click on:

• JBoss architecture
• Installation of jboss
• Advanced Java Training in Bangalore
• Session Configuration
• JBoss Tutorials
• JBoss Overview