Monday, October 14, 2013

Hot Deployment with IntelliJ IDEA

Recently there was a voting in the PrimeFaces forum PrimeFaces IDE Poll for the best IDE used to develop PrimeFaces applications. The most people voted for NetBeans. NetBeans and Eclipse are free IDEs. My favorite IDE IntelliJ IDEA Ultimate is not free and I think this is a reason why there are less people using it on the job. I thought it would be a good idea to show some nice features in IntelliJ. This post will demonstrate how to configure IntelliJ for the hot deployment when developing web projects. Hot deployment means you can change web resources or classes at runtime and the changes will be recognized immediately without server restart. An useful feature during development process. In the example, I will take the application server JBoss 7, but any other server can be configured in the same manner as well. A good introduction to IntelliJ and JBoss there is in the IntelliJ Wiki. For a general information regarding working with application servers in IntelliJ please refer this help page.

We assume, the application server is already configured. The next step is to configure an exploded WAR artifact for the web project. An exploded WAR is a decompressed web application archive, a directory structure that is ready for deployment on an application server. IntelliJ creates it automatically, but nevertheless, you should go to File --> Project Structure --> Artefacts and ensure that the exploded web application ends with the extension .war. If you use Maven, the exploded WAR is created below the target folder. More info on the help page.


You should also check if the Hot Swap is enabled. Go to the File --> Settings --> Debugger --> HotSwap and ensure that all checkboxes are checked and the radio button "Reload classes after compilation" is set to "Always".


As next step, click on the "Edit Configurations..." and go to the configured server. In the "Run/Debug Configurations" dialog, select "Update resources" in the drop-down "On frame deactivation". That means, when you switch to the browser, IntelliJ will copy resource files (JavaScript, CSS) from the source location (src/main/webapp) to the directory where it builds the exploded WAR to deploy.


Hot deployment for changed Java classes is resticted by JVM. E.g. the hot deployment for classes with changed method signature(s) doesn't work. But if you changed a method body, it will work. So, if you don't use JRebel which allows the hot deployment for classes being structurally modified, you can still rely on IntelliJ. All what you need to do for changes in Java classes is to recompile them. For that, you can go to the menu Build --> Compile or simple hit Ctrl + Shift + F9. After that, go to the browser and refresh the page to see changes.


8 comments:

  1. +1 Oleg and nice post, and LOL/smiling that that PrimeFaces IDE forum topic motivated/inspired you to write this blog.

    Hot deployment via IntelliJ...if not using JRebel (restart server and rebuild WAR). NetBeans does this as well. :)

    Per my experience, hot deployments can take its toll on servers, so need to set permsize, accordingly. Instead of doing a NetBeans-redeploy-or-restart, I prefer to stop server, deploy/drop-WAR, and start server (via NetBeans).

    How does IntelliJ handle the memory/PermGen issue(s) associated with 'hot deployment'(s)?

    ReplyDelete
    Replies
    1. "How does IntelliJ handle the memory/PermGen issue(s) associated with 'hot deployment'(s)?"

      Quite good. No issues until now. I have -XX:MaxPermSize=700m

      Delete
    2. Most likely you have a reasonably small application if the redeployment is an acceptable option for you.

      IntelliJ doesn't cope with PermGen in any way. PermGen issues are caused by classloader leaks and can't be prevented on the IDE level.



      Delete
    3. Yes, sure, PermGen issues are caused by classloader leaks. Almost every app server has the same issue after consecutively redeployments. So, a server restart can rescue.

      Delete
  2. "I have -XX:MaxPermSize=700m"

    I thought so. I did the same when i first started developing JSF web app via Glassfish 3.1.x; after setting max perm size to 384 or 512m and 'avoiding' hot deployments, i no longer had the (glassfish) permgen issues. and now, since i am using tomee and still avoiding hot deployments, and setting max perm size = 384m, i have no perm gen issues. :)

    "PermGen issues are caused by classloader leaks and can't be prevented on the IDE level. "

    well, if you 'avoid' hot deployments via your IDE, then you will definitely 'prevent' PermGen issues via/at-the IDE (level). :)

    ReplyDelete
  3. I have read your blog and got nice information about website designing & development company. Thanks!

    ReplyDelete
  4. This blog is very nice and with the help of Google search engine.

    http://www.favour.com.au/

    ReplyDelete
  5. Thank for sharing thoughts for salesforce developer. It's help for making best and innovative web application. This help for giving best ideas.

    ReplyDelete