The IRMA Community
Newsletters
Research IRM
Click a keyword to search titles using our InfoSci-OnDemand powered search:
|
Portal Development Framework
|
|
Author(s): Jana Polgar (Monash University in Melbourne, Australia), Robert Mark Braum (Monash University in Melbourne, Australia)and Tony Polgar (Coles Myer, Australia)
Copyright: 2006
Pages: 39
Source title:
Building and Managing Enterprise-Wide Portals
Source Author(s)/Editor(s): Jana Polgar (Dialog IT, Australia), Robert Mark Bram (Monash University in Melbourne, Australia)and Tony Polgar (Monash University in Melbourne, Australia)
DOI: 10.4018/978-1-59140-661-7.ch009
Purchase
|
Abstract
To understand portal applications and the principles of their development, we need to distinguish between a portal and a portlet. A portal is a framework that lets you plug in new features or extensions called portlets. In the same way that a servlet is an application component within a Web server, a portlet is an application component within a portal. A portal is a Web application. Developing portlets is the most important task in making portals function as the user’s window to information and tasks. Portlets are an encapsulation of content and functionality. They are reusable components that combine Web-based content, application functionality, and access to resources. Portlets must be considered as complete applications, having multiple states and view modes. They have messaging and event recognition capabilities. Portlets are assembled in portal pages that make up a portal implementation. An important issue is the design of a portal page as the aggregate of several different portlets.
Related Content
|
Jana Polgar.
© 2012.
6 pages.
|
|
Jun-Jang Jeng, Ajay Mohindra, Jeaha Yang, Henry Chang.
© 2012.
15 pages.
|
|
Jerh. O’Connor, Ronan Dalton, Don Naro.
© 2012.
15 pages.
|
|
Jana Polgar.
© 2012.
13 pages.
|
|
Tony Polgar.
© 2012.
13 pages.
|
|
Jana Polgar.
© 2012.
5 pages.
|
|
Andreas Prokoph.
© 2012.
19 pages.
|
|
|