After you write a Java class using the visual editor for Java, you can run it to test and debug the run-time behavior.
If the class has a public static void main(String[]) method, you can run or debug it as a Java application. However, when you write a Java bean using the visual editor for Java, it will not typically have a main method. Rather than adding a main method just to test the class, you can run or debug the class as a Java bean.
To debug a Java bean while you are testing it, you can switch to the Debug perspective, where the Java processes can be seen and where you can use breakpoints and step through the code.
Running a Java bean or application
While you are developing your visual class, you can run it to see its appearance and behavior.Configuring options for running a Java bean or application
You can specify different configurations for each Java bean or Java application that you run.Debugging a visual Java bean or application
If you want to see the Java processes and step through the code for your visual class while you are running it, you can choose the debug options.Advanced options for debugging Java beans
During normal development you should not need to be concerned with the VM that is used by each visual editor instance. Advanced users, however, can configure the workbench so that any messages sent to System.out or System.err of the VM are written to the .log file in the .metadata directory in your workspace.Testing and deploying applets
You can test an applet using launch configuration options before deploying it to open in a browser.Java bean exceptions
During normal development, exceptions are sometimes thrown by the Java beans. The visual editor displays icons and visual markers to indicate exceptions.
Parent topic: Editing Java in the visual editor
Related tasks
Running a Java bean or application
Configuring options for running a Java bean or application
Testing and deploying applets
Debugging a visual Java bean or application