Hot code replace in JBOSS4 and Eclipse3.1
If you are trying to debug your code using Eclipse, MyEclipse and JBOSS, then starting JBOSS via MyEclipse (in DEBUG mode) and setting your break points in Eclipse should be enough to trigger the debugger.
If you follow this method, please ensure that the WEB-INF/classes classes are not deployed when using the master-build script. This is fine for development and debugging but not for serious testing or production. Given the behaviour of the JBOSS class loader, having the same classes in more than one place can cause problems.
- Hot code replace is supported on JDK 1.4.x VMs, and IBM J9 VMs. Hot code replace is limited to changes which do not effect the shape of a class. That is, changes within existing methods are supported, but the addition or removal of members is not supported. Note that hot code replace and stepping on JDK 1.4.0 VMs was unreliable. The underlying VM problems were fixed in JDK 1.4.1.
- Hot code replace can not inspect most configuration file change,e.g., struts-config.xml, web.xml(works in Tomcat, not in JBoss) etc.