|
Portlet API 2 | ||||||||
| PREV NEXT | FRAMES NO FRAMES | ||||||||
AccessDeniedException is thrown if a portlet
attempts to access dynamic data in a manner that it is not
allowed to.ActionAdapter is an action listener in which all
callback methods are empty implementations.ActionEvent is sent by the portlet container when
an HTTP request is received that is associated with one more
actions.ActionListener interface must be implemented, if
an object wishes to receive action events.Capability class correspond to particular
properties which can be assigned to the client devices.Client interface represents the client device that
the user connects to the portal with.Event is the base interface for all events
that can occur whithin the portlet container.null if no such attribute exists.
null if no attribute with the given name exists.
null if no attribute with the given name exists.
null
if no such attribute exists.
null if the parameter does not exist.
null if this information is not available.
null if no such parameter exists.
InputStream object.
InputStream object.
true, it creates one and returns
it.
MessageAdapter is an message listener in which
all callback methods are empty implementations.MessageEvent is sent by the portlet container if
one portlets send a message to another.MessageListener interface must be implemented, if
an object wishes to receive message events.Portlet interface is used by the portlet container to
invoke the portlet.Mode class is a finite enumeration of
the possible modes that a portlet can assume.PortletAction can be implemented to defined
portlet-specific actions that need to be executed for specific
URIs.PortletConfig interface provides the portlet with
its configuration.PortletContext interface defines a portlet's view
of the portlet container within which each portlet is running.PortletException class defines a general exception that a
portlet can throw when it encounters difficulty.PortletLog provides the portlet with the ability
to log information, warning, or error texts.PortletMessage can be used for inter-portlet
communication.PortletPage contains information about the currently
visible page.PortletRequest encapsulates the request sent by the
client to the portlet.PortletResponse interface represents the response
sent to the client device.PortletSession holds the user-specific data that
the portlet needs to personalize the one global portlet instance.PortletTitle interface has to be implemented if
a portlet wants to support client, device, and/or user dependant
titles.PortletURI represents a URI to a specific portlet
function.PortletWindow represents the window that encloses
a portlet.SaxPortlet is an abstract implementation of the
Portlet that enables the use of SAX events to be sent
as the response.SaxPortletRequest encapsulates the request sent
by the client to the portlet.SaxPortletResponse interface represents the
response sent to the client device.service() call to this
method.
UnavailableException when the instantiation
of a portlet fails.User interface is an abstract view on the
user-specific data.WindowAdapter is a window listener in which
all callback methods are empty implementations.WindowEvent is sent by a portlet window whenever the
user or the portal interacts with its controls.WindowListener interface must be implemented, if
an object wishes to receive events from a portlet window.
|
Portlet API 2 | ||||||||
| PREV NEXT | FRAMES NO FRAMES | ||||||||