Information Technology Reference
In-Depth Information
However, using this model for AJAX-based portlet development requires
a lot of client-side JavaScript coding, especially using DOM to interact
with DHTML, which can be quite tedious and may cause JavaScript
cross-browser problems. Hence, for experienced AJAX developers,
the integration of AJAX into the portal can partially or wholly use
some third-party AJAX toolkits or libraries. For example, it has been
demonstrated that Direct Web Remoting (DWR) can be used in AJAX-
based portlet development although it involves extra coni guration and
usage learning.
11.2. 5
Survey of Tools and Technologies for Grid-Enabled
Portal Development
Currently, there are a variety of development tools, frameworks and com-
ponents that can support grid portal development. In order to provide a
guideline for grid portal developers to choose an appropriate toolkit, a
survey on major grid portal development tools and technologies that can
be employed to facilitate grid portal development has been conducted.
11. 2 . 5.1
GridSphere
The GridSphere Portal Framework [2] is developed as a key part of the
European project GridLab [35]. The development of the GridSphere has
combined the lessons learned in the development of the ASC portal and
the Grid Portal Development Kit (GPDK), which was a widely used tool-
kit for building nonportlet-based portals. The GridSphere provides an
open-source portlet-based Web portal, and can enable developers to
quickly develop and package third-party portlet Web applications that
can be run and administered within the GridSphere portlet container. One
of the key elements in the GridSphere is that it supports administrators
and individual users to dynamically coni gure the content based on their
requirements [8]. Another distinct feature is that the GridSphere itself
provides Grid-specii c portlets and APIs for grid-enabled portal develop-
ment. The main disadvantage of the current version of the GridSphere
(i.e., GridSphere 3) is that it does not support WSRP.
11.2.5.2
eXo Platform
The eXo platform [37] can be regarded as a portal framework and Content
Management System [36]. The eXo platform 1 was more like a portal
framework. The eXo platform 2 proposed a Product Line Strategy [38] as
it is realized that end-user customers need to get ready to use packaged
solutions instead of monolithic products. The eXo platform 2 is now a
core part on which an extensive product line can be built [38]. It features
Search WWH ::
Custom Search