Object models provide developers with a scripting environment by creating and instantiating objects—and exposing their properties, methods, and events.
In a distributed environment such as the Web, object models can be client side or server side. In a client script, objects belong to the Document Object Model of the client browser. In a server script, objects belong to the object model existing on or deployed to the selected server.
You can view representations of client-side and server-side object models in the Language page of the System Tree.
The Web Target object model streamlines the process of developing and deploying JSP applications. During the development phase, the object model hides many of the platform-specific details you would otherwise need to know to write server pages. At deployment time, the object model takes care of mapping your platform-independent code to each application server platform you choose to target.
The structures and objects in the Web Target object model are defined in Java classes for JSP targets.
When you deploy a JSP page that uses the Web Target object model, the target automatically adds an object model file to your deployed application and imports the contents of that file into your page. The object model file resolves references you make to JSP target objects to appropriate objects in the target application server. The deployment controller imports an object model file into any JSP file containing one or more server scripts that use the Web Target object model.
For more information about the Web target object model, see and “Using the Web Target object model”.
