364 Document Management Using WebSphere Portal V5.0.2 and DB2 Content Manager V8.2
10.1 Portlet design
Portlets should follow the Model-View-Controller design pattern (MVC). This
means that portlets have the general structure as outlined in Figure 10-1.
Figure 10-1 Model-View-Controller design of portlets
The portlets in the ITSO sample portlet application follow this design. In-depth
information about portlet development can be found in IBM WebSphere Portal V4
Developer’s Handbook, SG24-6897 and IBM WebSphere Portal V5, A Guide for
Portlet Application Development, SG24-6076.
Beans (Model)
The Model in a portlet application is not necessarily unique from the model in any
other Java server side application. The Model represents business logic and
should not be concerned with the Controller or the View. The Controller could be
a servlet, portlet, or simple Java class. The View could be a JSP or even simple
HTML.
In Figure 10-1, there is a SessionBean and a ViewBean. This distinction is made
because some data is only needed for the current request. Such data is
communicated to the View JSP by using the ViewBean. On the other hand, the
«use»
«use»
«invoke»
«use»
«use»
«invoke»

Get Document Management Using WebSphere Portal V5.0.2 and DB2 Content Manager V8.2 now with the O’Reilly learning platform.

O’Reilly members experience live online training, plus books, videos, and digital content from nearly 200 publishers.