Table of Contents Previous Section

A Note on Scripted Classes

The following sections discuss in detail the roles performed by the application (WOApplication), session (WOSession) and component (WOComponent) objects in request handling. In WebObjects, the behavior of these objects can be scripted or compiled. In the latter case, you would might create a subclass of, say, WOSession, and then implement the request-handling methods. Scripted behavior, however, is more common in WebObjects than compiled behavior. In a scripted application, you write WebScript code (or another supported scripting language) in an application's Application.wos and Session.wos files, and in each component's ".wos" files. At run time, the application uses a special subclass of WOApplication and WOSession---and a unique WOComponent subclass for each component---to generate instances. It makes the code it finds in the associated ".wos" files the implementation code of these subclasses.

For more on scripting, including the script files allowed in a WebObjects application, see the chapter "Using WebScript."

Table of Contents Next Section