Re: [Webwork-devel] JSR 162: Portlet API

[Mike Cannon-B. <mi...@at...>]

I=B9ll be interested to see how this turns out, especially as it's based on
JetSpeed which is a 'dead' Jakarta project (ie doesn't seem to have been
updated in ages, I can't find a single production site running it). Also it
used to have to have portlets coded in Java (as this seems to specify, it's
a portlet API like the servlet API). Anyone remember the days of coding HTM=
L
in a servlet? ;)

We'll wait and see I suppose.

Back to your regularly scheduled WebWork programming!

-mike

On 9/1/02 2:41 PM, "DeSouza, Edwin" (ede...@ja...) penned the
words:

> For more info:=20
> http://www.jcp.org/jsr/detail/162.jsp
>=20
> The Portlet API specification defines an API for web application componen=
ts
> that interact with and can be aggregated in web applications like portals=
. We
> refer to these components as portlets in the remainder of this text.
>=20
> Portlets are web components like servlets, but have additional, special
> properties that allow them to easily plug into and run in enclosing web
> applications like portals. Portlets are designed to be aggregatable in th=
e
> larger context of composite pages, e.g. multiple instances of the same po=
rtlet
> parameterized with different per-user, per-instance portlet data can coex=
ist
> on the same portal page. Usually, many portlets are invoked in the course=
 of
> handling a single request to aggregate their respective produced markup
> fragments in a page of markup. The markup fragments generated by portlets
> often need to contain links to trigger actions in the portlet, therefore
> URL-rewriting methods are required that allow portlets to transparently c=
reate
> links within the markup fragments they output, without needing to know ho=
w
> URLs are structured in the particular web application.
>=20
> Portlets rely on the portlet container infrastructure accessible via the
> Portlet API for functions like access to user profile information for the
> current user, access to the window object that represents the window in w=
hich
> the portlet is displayed, participation in the portal window and action e=
vent
> model, access to web client information, inter-portlet messaging and a
> standard way of storing and retrieving per-user/per-instance data
> persistently.
>=20
> The Portlet API provides standard interfaces for the functions mentioned
> above. The Portlet API extends the servlet programming model and defines =
a
> common base class and interfaces for portlets and tags for JSPs called by
> portlets, cleanly separating portlets from the surrounding infrastructure=
 so
> that portlets can run on different portal servers like servlets can run o=
n
> different application servers.
>=20
> The Portlet API specification shall evolve from the portlet concept as
> developed in the Apache JetSpeed Open Source project. In many aspects, th=
e
> Portlet API is an extension of the Servlet API, defining additional inter=
faces
> for portlet-specific functionality. In some other aspects, it restricts u=
se of
> functions provided by the Servlet API to the subset that makes sense for
> portlets just producing aggregatable markup fragments and not having owne=
rship
> of the entire page that displays them. For example, unlike servlets, port=
lets
> may not send errors or redirects as a response, this may only be done by =
the
> application that invokes and aggregates the portlets into a larger page.
>=20
> Portlets can be grouped in Portlet Applications. Portlets in one portlet
> application can exchange messages via the Portlet API. Portlet Applicatio=
ns
> are packaged, distributed and deployed using WAR files that include
> portlet-related meta-information, utilizing existing Servlet infrastructu=
re.
>=20
> The Portlet API shall be compatible with the Remote Portlet Web Services
> concept in the sense that portlets written to the Portlet API can act as =
local
> proxies in a portal server for remote portlet web services located on oth=
er
> servers and portlets written to the Portlet API can be wrapped into remot=
e
> portlet web services.
>=20



Sent using the Entourage X Test Drive.