Configuring IDE Debugging with JavaRebel
March 4th, 2008 by Jevgeni KabanovOne of the inconveniences that our users frequently report is stepping in/out of the code managed by JavaRebel. However we have found that most IDEs today provide a way to filter out JavaRebel methods and in this article we will show how to configure Eclipse and IDEA to make your debugging as pleasant as ever.
To configure Eclipse go to Window -> Preferences and from there to Java -> Debug -> Step Filtering (or just search for “Step filtering”). Enable step filters and “Filter synthetic methods”. Make sure that “Step through filters” is also on. Now enable all the default filters and add three package ones:
- RebelMethodAccessor*
- com.zeroturnaround.*
- org.zeroturnaround.*
Result should look like this:
In IntelliJ Idea open up debugger properties (File - Settings - Debugger). On the lower left corner of the debugger settings page make the necessary changes. Be sure to tick “Skip synthetic methods” checkbox and add the necessary class filters. See screenshot:
March 7th, 2008 at 4:05 am
Eclipse is still giving me “Source not found” pages in Java Editor when I try to step into a class (F5). In the call stack I see MyAction.__rebel_accessor__() on top and the class and method I’m trying to step into on the line below.
This is existing code but was reloaded by Rebel.
March 7th, 2008 at 11:04 am
Are you using the latest nightly build? Not everything was marked as synthetic before.
May 2nd, 2008 at 1:51 pm
[…] Improved debugging. No need to step through generated methods anymore, see this article. […]
August 31st, 2008 at 8:16 am
Hello, I am running Eclipse 3.4 and JavaRebel 1.2 and I am unable to add the package that results in the availability of “RebelMethodAccessor”. I have com.zeroturnaround.* and org.zeroturnaround.*. Any ideas?
August 31st, 2008 at 12:43 pm
In 3.4 they refactored this page and now you should use “Add Filter” button and “RebelMethodAccessor*” pattern.