[jboss-user] [JBoss Tools] - Re: Best Practice for Hot Deploy in JBoss AS 7 for JSF 2 + CDI + EJB 3.1 + JPA + Maven Project

henk de boer do-not-reply at jboss.com
Sun Jul 22 17:16:22 EDT 2012

henk de boer [https://community.jboss.org/people/henk53] created the discussion

"Re: Best Practice for Hot Deploy in JBoss AS 7 for JSF 2 + CDI + EJB 3.1 + JPA + Maven Project"

To view the discussion, visit: https://community.jboss.org/message/749441#749441

> Max Rydahl Andersen wrote:
> Depends what kind of hotdeployment you refer to.
> if updates to xhtml, html etc. kinda content then it should just work out of the box and changes should show up as soon as you refresh the browser.
> if you are changing .class or .jar's then there has never been such support in any AS version 

Actually, the support was there but it almost seems as if was a kind of hidden support that everybody plain forgot about.

The JVM infact does support class reloading natively, via a mechanism called +*hotswap*+ (see this for some more background:  http://java.dzone.com/articles/reloading-java-classes-401 http://java.dzone.com/articles/reloading-java-classes-401). As long as you're only changing code inside a method's body, the JVM will happily accept the changed class. The (WTP) deployer has to cooperate though and really deploy updated .class files. If the change is incompatible with what the JVM accepts, it should warn about that.

This has always worked in AS 4, 5, and 6.

Reply to this message by going to Community

Start a new discussion in JBoss Tools at Community

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-user/attachments/20120722/a01b5a3e/attachment.html 

More information about the jboss-user mailing list