Once you have edited your application code on the client, you need to compile, run, and debug on the server. You must create a launch configuration, which Atelier uses to run and debug programs you have developed. You can create a default configuration for a class or routine file from the context menu in the Atelier Explorer. Right click on a file containing a class or routine, and select Run As > Atelier Application or Debug As > Atelier Application. Atelier creates a launch configuration using information from the project and file you selected, and runs or debugs the file. The name of the configuration comes from the package and the class or routine. For class files, the entry point is the first class method in the class.
If you launch a configuration in Run mode, the application executes without stopping, even if breakpoints are set. A configuration launched in Debug mode stops at active breakpoints, allowing you to step through execution, examine variables, and perform other debugging tasks.
You can create new launch configurations or edit existing ones by selecting either Run > Run Configurations... or Run > Debug Configurations... from the main menu bar, or from the Run As or Debug As items in the Atelier Explorer context menu. The dialog box lists all the types of Run or Debug configurations you can create. The content of this list depends on the development tools you have installed, and configuration types you have chosen to filter in Window > Preferences > Run/Debug > Launching > Launch Configurations. Select Atelier Application from the list, and click the New button () to create a new launch configuration. The debug configurations dialog also lists Atelier Application Attach, which lets you create a debug configuration to attach to a running process.
You need to specify a project for the configuration. The connection associated with that project provides the server and port used to run and debug the application. You can run or debug using a class method, routine, or CSP file as the entry point. To use a class method, specify the class name and the name of a class method. To use a routine, specify the routine name and an optional label or offset in the routine, and arguments if required. To use a CSP file, specify the URL of the file. Setting a CSP file as the entry point lets you invoke it under control of the debugger. You can then interact with with your web application and step through the classes and routines it calls.
The Debug perspective provided by Atelier is similar to the Eclipse Debug perspective for Java in terms of the views and commands that are available. See topics on debugging in the Java Development User Guide for basic information on debugging in Eclipse. However, debugging applications written in ObjectScript differs in important ways from debugging in Java or many other popular programming languages. With most languages, you edit, compile, run, and debug entirely on your client machine. In ObjectScript development, you store and edit source code on the client, but compile and run on the server. When you debug, you use Atelier, which is running on the client, to observe the behavior of the application, which is running on the server. Debugging involves the transfer and synchronization of information between the server and the client.
ObjectScript also uses different terminology for variables of various type and scope. For historical reasons, the term "global" refers to multi-dimensional storage, so what most languages call global and local variables ObjectScript calls public and private variables. This terminology is used in the Variables view in the Atelier debug perspective. True ObjectScript globals do not appear in the Atelier Variables view, but can be examined in the Interactive Console view.
Creating an Atelier Launch Configuration
Debugging an Atelier Application
Running an Atelier Application
Atelier Explorer View