Uses of Package
org.sakaiproject.portal.api

Packages that use org.sakaiproject.portal.api

org.sakaiproject.portal.api
org.sakaiproject.portal.api.cover

Classes in org.sakaiproject.portal.api used by org.sakaiproject.portal.api

Editor
Interface to encapsulate information needed to register pluggable editors and use them within the Sakai portal and Tool system.

EditorRegistry

PageFilter

Portal
This interface represents a portal and is used mainly by portal handlers that will not know the details of the portal implimentation.

PortalHandler
Tools that want to add handlers into the portal URL space may impliment this interface.

PortalHandlerException
Throw when a portal handler fails to handle a request

PortalRenderContext
This interface represent the Render Context, it allows the portal implementation to put values into the render context.

PortalRenderEngine
Repesents the API used by the protal to comunicate with the RenderEngine implimentation.

PortalService
Portal Service acts as a focus for all Portal based activities, the service implementation should act as a holder to enable the varous webapps to communicate with one annother.

PortalSiteHelper

PortletApplicationDescriptor
Describes a Portlet application when it is loaded into the Web Container

PortletDescriptor
Describes the Portlet

SiteNeighbourhoodService
The SiteNeighbourhoodService provides a list of sites in the neighbourhood of the current context.

SiteView
This interface represents a view of a the Site cloud from a particuar view point.

SiteView.View

StoredState
Stored state is used to store the request state over a number of requests, It is used to restore state over a login sequence of during a direct placement into a tool state.

StyleAbleProvider
This interface should be implemented by a Stylable provider to control the portal in the browser either by CSS or by javascript manipulation of the DOM in the browser.

Classes in org.sakaiproject.portal.api used by org.sakaiproject.portal.api.cover

PortalService
Portal Service acts as a focus for all Portal based activities, the service implementation should act as a holder to enable the varous webapps to communicate with one annother.