Table of Contents 
Previous Section
Search Path for Reusable Components
When WebObjects encounters the name of a reusable component at runtime:
NAVCONTROL: NavigationControl {};
it must find a WOComponent object to represent the component and then find the component's resources (the HTML template file, image files, and so on).To find an object to represent the component, WebObjects looks in the runtime system for a subclass of WOComponent (in Java, Component) with the same name as the component ("NavigationControl" in the example above). For compiled reusable components this search should succeed, but for scripted ones it should fail.
Next, WebObjects looks within the application directory for the reusable component's resources. For example, if you manually start an application that resides in <DocRoot>/WebObjects/MyWOApps/Fortune.woa, the Fortune.woa directory will be searched.
If WebObjects doesn't find the component there, it assumes that the reusable component is included in a framework. It searches all frameworks that were linked in to the application executable for a component with that name. For example, applications written entirely in WebScript use the default application executable, WODefaultApp. This executable is linked to the frameworks WebObjects.framework and WOExtensions.framework, so any components defined in either of these two frameworks can be used in a scripted application.
Table of Contents 
Next Section