The VisualAge for Java IDE can run programs that dynamically load and run external classes. External classes are classes that have not been imported into the workspace, but rather reside in a .class file, Zip file, or Jar file on the file system. The path to the file must be part of the class path for the program.
If you want to debug such a program, you have the option of setting breakpoints on methods in the external classes.
To set a breakpoint on a method in an external class:
To access methods in a .class file that has been archived:
Now, the dialog lists all the .class files in the selected directory or archive. Select one to see the list of methods available for setting breakpoints.
Once the breakpoint is set, any thread that calls it will be suspended when the method is entered. External breakpoints cannot be conditional and do not display the breakpoint symbol in the source pane margin.
Putting Source Code on the Debug Source Path
If the source code for the method is available on the file system, and if the path to the
source code is included either in the class path or in the debug source path (set in the
Debugger Options), you will be able to step into the method code. The debugger looks
for the source code first in the class path, and if it cannot find it there, then in the
debug source path.
If the source is not available (not on either the class path or the debug source path), you will only be able to step over the method.
Clearing Breakpoints on External Methods
To clear a breakpoint from an external method, clear its check-box in the
External Method Breakpoints dialog. You may leave the method on the list so that it
is easily accessible if you want to set the breakpoint again later. If you want to
remove it from the list, however, select it and click Remove.
Setting Breakpoints in Source Code
Clearing and Disabling Breakpoints
Stepping Through Methods
Setting Debugger Options