Portal and Portlet interview questions and answers
Latest answer: ortlets are UI components that are pluggable and
are managed, displayed in a web portal. Markup code fragments are produced by
the portlets which are aggregated into a portal page...............
Read
answer
Latest answer: The core implementation of the portal is UI,
hosted by a Portal server. The HTTP requests, HTML responses, and returning
appropriate portal pages are handled by the Portal UI. Enterprise Web
application also can be handled by the Portal Server...............
Read answer
Latest answer: User identification across many requests and
transient information storage about the user is processed by PortletSession
interace. One PortletSession is created per portlet application per
client...............
Read answer
Latest answer: The portlet view of the portlet container is
defined by PortletContext. It allows the availability of resources to the
portlet. Using this context, the portlet log can be accessed..............
Read answer
Latest answer: The following are the reasons to use portals:
Unified way of presenting information from diverse sources...............
Read answer
Latest answer: Horizontal Portals: These are the portals are of
type general interest. Yahoo!,Lycos,AOL,Freeserve,Sympatico are examples of
horizontal portals...............
Read answer
Latest answer: Highly integrated web applications’ costs reduce
by portals. JBoss enables the reusability of branding and deploying new
applications of composite nature...............
Read answer
Latest answer: PSML was created to allow abstraction and
content structure within Jetspeed. It has two markups:..............
Read answer
Also read
Rich user interfaces can be achieved by using a combination of dynamic HTML
elements such as HTML and JavaScript. However, the scope of such an interface
is limited to client-side behavior and has minimal functional implications due
to the lack of server-side interactions.
AJAX has gained tremendous popularity in the traditional web application
development world due to the richness and agility that it brings to user
interfaces. Portals, such as JBoss portal, can also gain signifi cantly from
AJAX, in terms of implementation of both behavior and functionality.
Before we look at the features and options provided by the new specifi cation,
let's look at how traditional JSR-168 portlets functioned. As shown in the
following fi gure, the "Action" request invoked the processAction method on the
server, which implemented controller logic to route it to the correct view.
Among the set of features that the new portlet specifi cation JSR-286 introduces
to make things easier for AJAX implementations, are the options to directly
communicate with the portlet through shared render parameters and resource
serving.
Implement AJAX functionality in one of the portlets, using asynchronous server
calls and dynamic HTML.
JBoss portal supports markup through tags on layouts and renderers of the pages.
Special tags are added to layout JSPs that facilitate the placement of AJAX
features on a page. Similarly, renderers are used to interpret the tags and to
render AJAX-driven content. The obvious advantage is the in-built support for
the auto-creation and control of AJAX components on portal pages.
Whereas the layout and renderer contribute to AJAX behavior at the markup level,
JBoss portal's support for object-level confi guration can be leveraged to
provide AJAX support at the page level. The object property inherits a confi
gured behavior from its parent. Currently, two features are offered for
AJAX-driven content
Although AJAX is an exciting technology and provides signifi cant advantages in
terms of performance, usability, and implementation, there are certain
scenarios where using AJAX is not a good fi t. This is especially true when a
lot of custom development is involved in using AJAX libraries.
|
