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

[Philipp M. <me...@o-...>]

On Wed, Jan 09, 2002 at 10:50:09PM +0100, Rickard wrote:
> >Portlets rely on the portlet container infrastructure accessible via the=
=20
> >Portlet API for functions like access to user profile information for=20
> >the current user,
>=20
>=20
> WebWork Action *Aware interfaces.

Nope, the aware interfaces won't give you a persistent storage of the
users profile. Although one could pass the reference to user manager into
the action via ApplicationAware.

> >access to the window object that represents the window=20
> >in which the portlet is displayed,=20
>=20
> What does this mean?
>=20
> >participation in the portal window=20
> >and action event model, access to web client information,=20
>=20
> WebWork Action *Aware interfaces.

Rickard, I think you got this one wrong. I'm not sure but I think by
accessing the "window object" the spec will give you a way to "roll-up",
close and rearrange the portlets on the page (like my.netscape.com
does). The event model will supplement this, I suppose by providing
listeners for these "window"-events.

> >inter-portlet=20
> >messaging=20
>=20
> ActionFactory.getAction()

I doubt this already does the jobs ;-)) Although I don't know what
inter-portlet-messaging would be good for.

> >and a standard way of storing and retrieving=20
> >per-user/per-instance data persistently.
>=20
> SessionAware.setSession().

Persistently! See above.

Rickard, I don't see much benefits in this JSR either, but webwork
alone won't do the job. Correct me if I'm wrong, it was you who did some
portlet developing a xpedio IIRC. I really love webwork and I don't like
this JSR but webwork is not the golden hammer.

-billy.
--=20
Philipp Meier                              o-matic GmbH
Gesch=E4ftsf=FChrer                  Pfarrer-Wei=DF-Weg 16-18
Tel.: +49-(0)700-66284236                     89077 Ulm