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? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3921729#3921729 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3921729 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
