This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hot deployment is already a JBoss AS capability - overwrite an existing WAR file, for example, and the app is redeployed. The hot deployer scans the deploy directory every 5 seconds looking for changes. You can, of course, turn the hot deployer off and/or change the frequency at which it scan the deploy directory.
If you have an exploded deployment (a *.war directory rather than a *.war file, for example), then updating the key configuration files (web.xml fior WAR, application.xml file for EAR, for example) will cause the hot deployer to redeploy the app.
Doing this via Eclipse so that you can debug the app? Which I imagine involves Eclipse releasing the current set of classes for your app and then latching onto the updated ones so that you can continue debugging. Haven't the fainest idea. I'll leave it up to Jaikiran as to whether this topic should be moved to the IDE forum.
Peter Johnson wrote:
Doing this via Eclipse so that you can debug the app? Which I imagine involves Eclipse releasing the current set of classes for your app and then latching onto the updated ones so that you can continue debugging. Haven't the fainest idea.
I have heard that IDEs have the ability to swap the code when being run in debug mode. I personally haven't tried this with any of the IDEs for various reasons.
Start JBoss in debug mode from eclipse and make sure build automatically is enabled that is it.
This however, isn't a application server specific thing, but more of a IDE thing, so i guess the IDE forum is a good place for this.