If Client-Side Components Do Not Work

After you install WebObjects, the Java client-side components feature should "just work" (assuming you have a Java-enabled browser). Unfortunately, files are inadvertently moved or deleted sometimes. The following checklist will assist you in situations like these. For Java client-side components to work, the following parts must be in place.

You must have a Java-enabled browser.
The following packages and classes must be installed in DOCUMENT_ROOT/WebObjects/Java:

next.util.PropertyListUtilities.class
next.util.KeyValueCoding.class
next.wo.client.Association.class
next.wo.client.SimpleAssociation.class
next.wo.client.SimpleAssociationDestination.class
In addition, the next.wo.client.controls package, which contains the applet classes (TextFieldApplet, ButtonApplet, and so on), must be installed in the same location. See "Client-Side Applet Controls" for descriptions of each supported applet.

When NeXT's Java package is installed, it is written to NEXT_ROOT/NextLibrary/Java as well as to DOCUMENT_ROOT/WebObjects/Java. If your DOCUMENT_ROOT has been deleted or corrupted, you can copy the packages in NEXT_ROOT/NextLibrary/Java to DOCUMENT_ROOT/WebObjects/Java.

Of course, if you intend to create your own applets or Association subclasses, or do other Java development, you must obtain Sun's JDK (Java Development Kit) or a similar product.

If you install the development version of WebObjects, you get examples of applications that use client-side components in NEXT_ROOT/NextDeveloper/Examples/WebObjects and example applet controls in the next.wo.client.examples package (installed in both NEXT_ROOT/NextLibrary/Java and DOCUMENT_ROOT/WebObjects/Java). The TimeOffJava example application contains the source code for the controls in next.wo.client.examples. You are strongly encouraged to read the application's ReadMe file before attempting to compile this source code.

Note: If Java client-side components don't seem to work on your system, do not set the CLASSPATH environment variable to point to the next.* packages in DOCUMENT_ROOT. Doing so might seem to resolve the problem, but this is true only in those situations where the browser and server reside on the same machine.

Table of Contents Next Section