What Goes Into the StudioManager Application

As with most Java Client WebObjects applications, you create the Java Client StudioManager application using the following ingredients:

• A model you produce using the EOModeler application provided with Enterprise Objects Framework. A model defines a mapping between your enterprise objects and data in a relational database.

• A user interface. You use Interface Builder to construct a Web-based user interface that can interact with the Java Client. You must load a special palette (EOJavaClient.palette ) as well as the standard EOPalette.palette . With the EOJavaClient.palette you can compose a user interface made from "widgets" derived from the Java Foundation Classes (JFC), informally known as Swing. Your application can also have pages dynamically generated entirely from objects on the server; for help in composing these pages, use WebObjects Builder.

• Web components . The Main component is automatically set up to have a WOJavaClientApplet component that is bound to the interface controller on the server. You can add other Web components with or without a Java Client linkage. Also provided are "skeletal"implementation files for the server-side application, session, and direct-action objects as well as API bindings files for server-side components.

• Source code for enterprise object classes. In the StudioManager application, these are Studio and Talent. Movie uses the default enterprise object class, EOGenericRecord, since it has no custom behavior. This is described in more detail in later sections.

In this tutorial you'll learn the basic things you must do to create a Java Client WebObjects application. You'll discover how to:

• Create a new project using Project Builder.

• Create a new model based on the Movies database using EOModeler.

• Edit your project's nib file in Interface Builder.

• Write source code for the Studio and Movie enterprise object classes.
• Build your project in Project Builder.

Previous | Back Up One Level | Next