Limit debugging to only classes that the devloppment team programs: Quite often when debugging, i am receiving a "source class not found" error while debugging (while the code enters JBOSS specific classes), i was wondering if it was possible to create an option that would step into/over BUT to the next line of code written by us.
While debugging my program, i am not interested in knowing that i enter object.class or things like this and i get confused. It would be very interesting to stop to the next line of code written by ourself, allowing us to debug a full call from the client in only one time. of course, an option allowing us to revert back to original debugging system would be available. Concerning this debugging system, it would be great to have a call tree to see which method called with one and so on. Degugging would be a lot more clear (this call tree would also take benefits from the "Dev classes" debugging system just described above). The last thing i whishe about JBoss IDE debugging system would be to be able to see the currently loaded EJB, their state and all information that can be shown about them. This would give another view of the Application and would probably help a lot of people out here. I don't know if somebody else is interested in theses enhancements but, anyway, thank you for even reading them. Jerarckill View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3847522#3847522 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3847522 ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
