• support.sas.com

• Knowledge Base

• Support

• Training & Bookstore

• Community

Developer Resources

• Reference
• Examples
• Product Information
• SAS Notes
• Software Downloads
• System Requirements

Products

• webAF Software
• webEIS Software
• SAS/IntrNet Software
• SAS/AF Software
• SAS Integration Technologies

Technologies

• Applets/Applications
• Web Applications
• Wireless Apps

API Reference

• Component API
• J2SE API
• J2EE API

SAS AppDev Studio 3.0 Developer's Site

Navigating and Managing Files in Your Project

Using the Project Navigator

The Project Navigator view, located by default on the left side of webAF, has five tabs along the bottom. The tabs are used to select which kind of information to display:

• Components - displays a tree of SAS components or tags in your project.
• Files - displays a tree with all file names in your project.
• Project Classes - is generally not meaningful for Web applications.
• All Classes - displays a tree of the packages and the classes that are available in JAR files.
• Help - displays a tree of available documentation.

The tree in the Components tab can be organized in four different ways, selectable by the drop-down list button on the caption of the navigator view:

• Flat View - shows all components in a given file at the same level in the tree, with attributes listed for each component.
• Containment View (no details) - shows the nesting relationship of components, without any attributes.
• Containment View (full details) - shows the nesting relationship of components, with attribute names shown.
• Scope View - shows components grouped by scope. The main branches under the project node are Servlet Context scope (also known as application scope), Session scope, and nodes for the individual file names. Request and Page scope nodes will be found under each file name. Expanding a scope name node will display all components that have that scope.

You can quickly locate where a component is used by right-clicking on the component in the Components tab of the Navigator, and selecting Go To Source from the pop-up menu. Instances of components that are shared between files can be easily be determined by selecting Scope view and expanding the Servlet Context or Session scope nodes as appropriate. Then expand the component node of interest under that scope to see all locations where it is used.

The tree in the Files tab can be organized two ways, based on the selector on the caption:

• Flat view - shows every file in the project as a branch off the project node.
• Explorer view - shows a tree hierarchy organized by directories.

In Files view, <webappbase> represents the Web application base directory. The base directory can be determined by selecting File Project Properties and choosing Options. For either Flat view or Explorer view, only files explicitly contained in the project will be shown. For example, if you copy a file from somewhere else to your project directory or one of its sub-directories, it will not show up in either view until you add it to the project.

Note that in the Files view, clicking on a filename will not change which editor view window is currently selected, but double-clicking a filename will select that editor frame (opening it if necessary). Clicking on a different editor frame will not change the selected filename in the File view. Do not assume that the filename selected in the Files view is the file that you are editing. Instead look at the caption for the Editor frame to determine the filename that you are editing.

Adding and Removing Files From the Project

Files created by webAF using the File New wizard will, by default, be included in your project. However, simply placing files in or under your project directory does not imply inclusion in the project. In particular, if you use the new project wizard to import an existing Web application, the files copied from that Web application will not automatically become part of the project.

It is important to include source files as part of the project, because if you do not, those files will not be included in the build. Even if you edit a Java file under the project directory, save it, and then select Build Rebuild All, this file will not be compiled. This is because webAF automatically regenerates the build.xml file by including all files in the project when the project is built. Therefore it is important to explicitly add any source files to the project.

To add a file or group of files to the project, select Insert File Into Project, navigate to the directory, and then select the files that you want to add.

To remove a file from the project, select the file in the Navigator's Files tab, right-click and select Remove From Project. Note that removing a file from the project does not delete the file, nor does it close any editor view for that file that might be open.

Copying or Renaming a Web Application Project

To make a copy of the current project in a new location, select File Save Project As. In the dialog, enter the new project name, project directory, and optional default package name, and then click OK.

Important Note: In webAF 3.0, you will then need to manually delete the *_build.xml file (where * represents the new project name), and then rebuild the project. If you omit this step, running the package-war build task will erroneously generate the WAR file in the original project instead of the new project. If you manually added other build targets to the *_build.xml file in the original project, then you will need to manually add back those targets to the file in the new project.