This document describes the structure and behavior of WebApp objects in the IBM® WebSphere® Portlet Factory system.
The information in this document is useful for:
- Developers creating WebApp models: Regardless of which builders are used when creating a model, the resulting application follows the WebApp structure and execution behavior. Developers creating models can view the WebApp generated for a Model by using the WebApp views in WebSphere Portlet Factory Designer.
- Others wanting to understand the model generation and execution process.
A WebApp is the executable result of generation for a WebApp parametric model. The WebApp elements are the fundamental building blocks that are available for builders to use when generating an application.
A WebApp represents all or part of a J2EE web application, and includes:
- Pages (JSP)
- State data (primitive, XML, and Java object)
- Links to business objects and other supporting objects
- Execution logic and generated Java code
- Event handling
- Links to other WebSphere Portlet Factory WebApps
There are far more WebApp builders than there are types of WebApp elements, because builders can use these fundamental building blocks in an unlimited number of ways.
This information describes the WebApp runtime environment process as well as the APIs that are to be used by a WebApp application developer.
The WebAppAccess is the programmer's interface into the running application.
Method and LJO method calls
WebApp methods and action lists are converted into a generated Java class that represents all the WebApp methods and action lists.
Overview: communicating between models
If your IBM WebSphere Portlet Factory application utilizes more than one model for its functionality, you may need to send data from one model to another.
Parent topic: Overview of IBM WebSphere Portlet Factory Designer