Apple WebObjects 3.5: Serving User Manual

Page 19

Advertising
background image

Serving WebObjects

20

application’s

.woa

directory and execute

WODefaultApp

, which is located in

NeXT_ROOT

/NextLibrary/Executables

.

-debug ON|OFF

Sets whether the application prints messages to standard output during startup.
By default, this option is ON. If this option is ON, the application prints mes-
sages such as the following:

Aug 22 18:08:46 WODefaultApp[423] Application Path:

/NextDeveloper/Examples/WebObjects/HelloWorld

Aug 22 18:08:50 WODefaultApp[423] Application Base URL:

/WebObjects/Examples/HelloWorld

Aug 22 18:08:50 WODefaultApp[423] Application Name:

Examples/HelloWorld

Aug 22 18:08:51 WODefaultApp[423] Reading WebServer configuration

from /NextLibrary/WOAdaptors/Configuration/WebServerConfig.plist.

Aug 22 18:08:51 WODefaultApp[423] Opening application's URL in

Browser:

http://localhost/cgi-bin/WebObjects/Examples/HelloWorld

Aug 22 18:08:54 WODefaultApp[423] waiting for requests...

-browser ON|OFF

Sets whether the application automatically starts up the web browser. The
default is ON. If this option is ON, the browser automatically opens a new
browser window (starting up the browser if necessary) with the WebObjects
application’s URL.

-m ON|OFF

Enables or disables monitoring. The default is ON. If this option is ON and you
manually start up an application, the application tries to find a running Monitor.
If it finds one, Monitor can automatically locate the application and display
information about it, provided an instance number is given with the adaptor’s

-n

option as described below.

-mhost

hostname

| subnet

The application tries to find a running Monitor on the machine named hostname
instead of on the local machine. If

subnet

is used, the application looks for a run-

ning Monitor in its network subnet.

-c

Requests that the application cache component definitions (templates) instead
of reparsing HTML and declaration files upon each new HTTP request. By
default, applications do not cache component definitions. This setting ensures
that during development of scripted applications programmers can modify a
component’s logic and see the result without having to relaunch the application.
If you are deploying applications, however, you should turn on component-defi-
nition caching by specifying this flag when you launch the application.

Advertising