The ingredients of a webobjects application – Apple WebObjects 3.5 User Manual
Page 19
19
WebObjects is a product that makes it easy for you to write dynamic web-
based applications (or WebObjects applications). Before you start
programming, however, you need to understand what a WebObjects
application is.
This chapter answers the question what is a WebObjects application in two
ways: first by showing you the pieces of a simple WebObjects application,
and then by explaining what happens when a WebObjects application runs.
In the rest of Part 1, you’ll learn how to construct these pieces and you’ll get
more in-depth information about how they work.
Read this chapter if you want a very high-level overview. The rest of this
book provides much more detailed information about how WebObjects
applications work and how to write one.
When you’re ready to start programming, read the book Getting Started With
WebObjects. It provides a series of tutorials that help you understand the tasks
and tools involved in writing a WebObjects application.
The Ingredients of a WebObjects Application
WebObjects applications reside within a directory named
WebObjects
in your
web server’s document root (
). Look in
, and you’ll see several directories.
These are WebObjects application projects, provided with the WebObjects
package as examples that you can use when learning WebObjects. These
examples range from simple to highly complex. For now, you might want to
focus on two of the simplest applications, named
HelloWorld
and
Visitors
.
When you look inside any of these project directories, you may see these
pieces:
•
.wo
directories, which are called components. Components are dynamic
HTML pages.
•
An application code file (
Application.wos
), which creates and manages
applicationwide resources.
•
A session code file (
Session.wos
), which creates and manages sessionwide
resources.
•
Standard project files, such as makefiles.