• Table of Contents
• Previous Next

Table of Contents Previous Section

The Ingredients of a WebObjects Application

In its simplest form, a WebObjects application contains these ingredients:

• Dynamic HTML pages (called components)

• WebObjects classes that provide an infrastructure for the web application

• An application executable that responds to requests from a web browser

Of these ingredients, you only have to provide the components. Create an application directory under <DocumentRoot>/WebObjects (<DocumentRoot> is your HTTP server's document root), and place the components in that directory. The application directory must have the extension .woa.

A default application executable is provided as part of the WebObjects product. The executable uses instances of the WebObjects classes to receive requests from a web browser and responds to them using the components that you provide.

More complex WebObjects applications may also contain:

• An optional application script that creates and manages application-wide resources

• An optional session script that creates and manages session-wide resources

• Optional compiled code that implements custom data and logic (WebObjects Pro and Enterprise only)

For information on using application or session scripts , see "The Role of Scripts in a WebObjects Application" in the chapter "Using WebScript." For information on including compiled code, see "Creating a Compiled WebObjects Application" in Getting Started With WebObjects Builder.

Table of Contents Next Section

Legacy Legacy Mac OS X Reference Library WebObjects 3.1 Developer Documentation