Creating Development Resources
The creation of development resources from the workbench typically involves using a wizard to generate files, then using an editor to edit those files. Interstage Studio provides wizards for generating various types of files and the editors for editing these files.
Build is a generic term referring to the creation of executable files from source files. Workbench invokes a builder to execute build tasks. What kinds of builders are invoked is determined by the type of project being built.
For example, the task of compiling Java source files to create a class file is one build task, and the function is provided by the Java builder.
There are two types of build, as follows:
Incremental build: A method that builds only the source that has changed
Clean build: A method that deletes all existing build results, then rebuilds all the development resources
Usually, an incremental build is performed. To perform a clean build, the user must explicitly clean the project beforehand.
Build is performed on the following two occasions:
Automatic build: When a source file is changed and saved, a build is performed automatically
Manual build: When a user executes a build manually by using the menu
Automatic builds are performed as the default. Therefore, users do not need to be aware of build tasks.
If a compile error, warning, or other information (collectively referred to as "problems") is output during a build, these are displayed in the Problems view. When a user double-clicks on a problem displayed in the Problems view, the source line for which the problem was issued is displayed in an editor. Compile errors, warnings, and any other problems are also indicated in an editor. As an example of this, a marker indicating an error may be displayed in the vertical ruler at the left edge of the editor area, or a squiggle may be displayed at the place of the problem.
Point
If an automatic build is performed every time source files are saved during a large-scale development, this may hinder user operations. If so, the timing of the build function can be controlled by setting manual build in order to minimize the hindrance to user operations.
Checking Application Operation
Applications that have been created can be executed and debugged from the workbench.
Use a launch configuration to execute and debug an application. A launch configuration registers the various settings required for execution of the application. For example, the application server and the Java VM launch options can be set. A launch configuration is convenient because, once it is created, it can be used for repeated execution and debugging of the application.
