Portlet interface is used by the portlet container to
invoke the portlets. Every portlet has to implement this interface,
either by directly implementing it, or by using an existing class
implementing the Portlet interface.
A portlet is a Java technology-based web component. It is managed by the portlet container and processes requests and generates dynamic content as response. Portlets are used by portals as pluggable user interface components.
The content generated by a portlet is called a fragment. A fragment is a piece of markup (e.g. HTML, XHTML, WML) adhering to certain rules and can be aggregated with other fragments into a complete document. The content of a portlet is normally aggregated with the content of other portlets into the portal page.
The portlet container instantiates portlets, manages their lifecycle and invoking them to process requests. The lifecycle consists of:
init method
destroy method
Request processing is divided into two types:
processAction method,
to perform actions targeted to the portlet
render method,
to perform the render operation
| Modifier and Type | Method and Description |
|---|---|
| public void | destroy()
Called by the portlet container to indicate to a portlet that the portlet is being taken out of service. |
| public void | init(PortletConfig
a config)PortletConfig object
containing the portlet's
configuration and initialization parametersCalled by the portlet container to indicate to a portlet that the portlet is being placed into service. |
| public void | processAction(ActionRequest
the action request request, ActionResponse the action response response)Called by the portlet container to allow the portlet to process an action request. |
| public void | render(RenderRequest
the render request request, RenderResponse the render response response)Called by the portlet container to allow the portlet to generate the content of the response based on its current state. |
| destroy | back to summary |
|---|---|
| public void destroy() Called by the portlet container to indicate to a portlet that the portlet is being taken out of service. Before the portlet container calls the destroy method, it should allow any threads that are currently processing requests within the portlet object to complete execution. To avoid waiting forever, the portlet container can optionally wait for a predefined time before destroying the portlet object. This method enables the portlet to do the following:
| |
| init | back to summary |
|---|---|
| public void init(PortletConfig config) throws PortletException Called by the portlet container to indicate to a portlet that the portlet is being placed into service. The portlet container calls the The portlet container cannot place the portlet into service
if the
| |
| processAction | back to summary |
|---|---|
| public void processAction(ActionRequest request, ActionResponse response) throws PortletException, IOException Called by the portlet container to allow the portlet to process
an action request. This method is called if the client request was
originated by a URL created (by the portlet) with the
Typically, in response to an action request, a portlet updates state based on the information sent in the action request parameters. In an action the portlet may:
A client request triggered by an action URL translates into one action request and many render requests, one per portlet in the portal page. The action processing must be finished before the render requests can be issued.
| |
| render | back to summary |
|---|---|
| public void render(RenderRequest request, RenderResponse response) throws PortletException, IOException Called by the portlet container to allow the portlet to generate the content of the response based on its current state.
| |