IntelliJ IDEA结合WildFly：企业应用XHTML及Backing Bean热部署问询

Absolutely! IntelliJ IDEA absolutely supports hot-reloading changes without full rebuilds and redeploys—this is a huge time-saver for Java EE/Jakarta EE projects like yours. Let’s break down how to set this up for your specific scenario (XHTML files and Backing Beans):

XHTML Files (Immediate Hot-Reload) #

For view files like XHTML, IDEA has built-in support that can work almost instantly, as long as you tweak a few settings:

• Open Settings/Preferences → Build, Execution, Deployment → Compiler, then check Build project automatically.
• Press Ctrl+Shift+A (Windows/Linux) or Cmd+Shift+A (Mac), search for Registry, and enable the compiler.automake.allow.when.app.running option.
• In your server's Run/Debug Configurations, set On 'Update' action to Update resources and On frame deactivation to Update resources. Now, whenever you edit an XHTML file and switch away from IDEA (like to your browser), the updated file will automatically sync to the server—just refresh your browser to see changes, no rebuild needed.

Backing Beans (Hot-Swap or Dynamic Class Reload) #

Backing Beans are Java classes, so hot-reloading here depends on whether you're making simple or complex changes:

• Basic HotSwap (for method body changes)
  If you only modify method logic (no adding/removing fields/methods, no changing inheritance or annotations), JVM's native HotSwap can handle this. Just run your server in Debug mode (not regular Run mode), edit the code, then press Ctrl+F9 (Windows/Linux) or Cmd+F9 (Mac) to trigger compilation. IDEA will swap the updated class into the running JVM instantly—no server restart required.
• Enhanced Hot-Reload (for structural changes)
  If you need to add fields/methods, modify signatures, or adjust class structures, native HotSwap isn't enough. You have two solid options:
  • JRebel: Install the JRebel plugin in IDEA (paid with free trial). It integrates seamlessly with your server config, supports nearly all code changes (including class structure edits), and auto-detects updates in both your gui.war and core.war modules without manual triggers.
  • DCEVM: Replace your JVM with the Dynamic Code Evolution VM (open-source). Then go to Settings/Preferences → Build, Execution, Deployment → Debugger → HotSwap and check Use dynamic class reloading. This lets you reload more complex class changes than native HotSwap.

Handling Your Multi-WAR Project (gui.war and core.war) #

Since you have two separate WAR modules, make sure these steps are covered:

• Ensure both modules are configured to use the global auto-compile settings mentioned earlier. Double-check each module's Module Settings → Paths to confirm the compile output directory is correctly set.
• In your server deployment config, add both gui.war and core.war as deployment artifacts. Set On 'Update' action to Update resources and classes if you want to hot-reload both views and beans across modules.
• If you're deploying the WARs together (e.g., in an EAR), verify your server recognizes module dependencies to avoid classloading conflicts during hot-reload.

Quick Notes #

• Some edge cases (like modifying static initializers, serialization logic, or certain annotations) may still require a full server restart, but 90% of daily development changes will work with the above setup.
• Different app servers have slight variations: WildFly has strong native hot-deployment support that pairs well with IDEA, while Tomcat may need reloadable="true" set in its context.xml (IDEA usually handles this automatically for you).

内容的提问来源于stack exchange，提问作者Vadim