0 Replies Latest reply on Feb 5, 2006 8:19 AM by Sz Fab

    Hot code replace failed - Hierarchy change not implemented

    Sz Fab Newbie

      How to make JBoss more resistant to class exchange during debugging?

      Scenario:
      I run JBoss from Eclipse using my own launch configuration. In many classess (beans implementation) I have to restart JBoss even after a really simple change to the class (e.g. adding System.out.println() ).

      Can I trick something in the JBoss configuration regarding the classloaders or in launch configuration parameters to make running JBoss more eager to work with changed classes?