Portal and Workflow in Grid Computing: From Application Integration to Service Integration - Grid Computing: Infrastructure, Service, and Applications - page 282

that it adopts Java Server Faces and the released Java Content Repository
(JCR-JSR 170) specii cation. The eXo platform 2 adopts JSR-168 and
supports WSRP.

11. 2 . 5. 3 Liferay Portal

The Liferay portal [39] is more than just a portal container [36]. It comes
with helpful features such as a content management system (CMS), WSRP,
and SSO. It is open-source, 100% JSR portlet API and WSRP compliant.
Liferay is suitable for enterprise portal development. Institutions and
companies that adopted Liferay to create their portals include Educa-
Madrid, Goodwill, Jason's Deli, Oakwood, and Walden Media [36].

11. 2 . 5.4 Stringbeans

Stringbeans [40] is a platform for building enterprise information portals.
The platform is composed of three components: (1) a portal container/
server, (2) a Web services platform, and (3) a process automation engine.
Currently, the portal server and Web services platform have been released.
The process automation engine will be released in the near future [40]. It
is JSR-168 compliant and supports WSRP. Stringbeans was used in the UK
National Grid Service (NGS) portal [41].

11.2.5.5 uPortal

uPortal [42] is a framework that aims to produce a campus portal. It is
now being developed by the JA-SIG (Java Special Interest Group). It is
JSR-168 compliant and supports WSRP. uPortal is widely used in creating
university portals (e.g., the Bristol University staff portal) due to its built-in
support. It is the only open-source portal framework that supports maxi-
mum types of portals ranging from Java portals to HTML portals, text
portals to XML portals [36]. However, documentation of uPortal is not
considered to be good and is not up to date. Most of the tutorials for uPor-
tal are written by students doing their theses. Documentation related to
uPortal is scattered about in several places such as the uPortal Website, a
conl uence-based wiki, email lists, the uPortal issue management system
(using Jira), and external sources.

11. 2 . 5.6 Pluto

Pluto is a subproject of the Apache Portal project. It is the reference imple-
mentation of the JSR 168 [1]. Pluto simply serves as a portlet container that
implements the Portlet API and offers developers a working example plat-
form to test their portlets. However, it is cumbersome to execute and test
within the portlet container without a driver (i.e., portal). Pluto's simple