Documentation Archive Developer
Search
PATH Documentation > WebObjects

Previous 

The Structure of a Direct to Web Project

A Direct to Web project has a structure similar to other WebObjects application projects. A newly created project contains three components, each enclosed in a subgroup, which you can access if you disclose the contents of the Web Components group in the Groups & Files list in Project Builder's main window.

You can add code to the .java files corresponding to each component to extend their functionality. See "Modifying Your Application's Code" (page 130) for more information on the Direct to Web API.

Each of the subgroups that contains a component also holds the component's .api file. This file specifies the exported keys, both optional and required, for each the component.

As you run your application, Direct to Web creates additional pages, using information in your model file and the settings specified in the WebAssistant. These pages do not show up as components in your project. Rather, Direct to Web creates them dynamically using a set of reusable components in the Direct to Web framework. However, you can generate components or user templates. When you do that, you can modify the resulting components just as you would with any other WebObjects components. See "Generating Components" and "User Templates" for more information.

The Resources group contains the model file you specified when you created the project (in this example, Movies.eomodeld). It also contains user.d2wmodel, which stores the preferences you have specified using the WebAssistant. Advanced users can edit this file; see "The Rule System" for more information about the rule file.


Previous 

© 2001 Apple Computer, Inc.