I agree, I would prefer for the portlet to be unaware of the other items on
the container, and the communication to/from them be controlled via some
sort of event mechanism. Maybe we can have various levels of compliance or
dependencies that a portlet has and can expose via its definition.
-----Original Message-----
From: PAVLIK,GREGORY (HP-NewJersey,ex2) [mailto:]
Sent: Wednesday, April 17, 2002 10:36 AM
To: ''
Subject: [wsrp] Are WSRP services aware of their page?
The notion seems to be emerging in JSR 168 that a portlet should be able to
obtain from it's request context a "view" of it's page, including at least
information about the other portlets in the page. This way, portlets can be
coupled together to make decisions based on whether "partner" portlets are
present on the same page.
Is something we intend to support in WSRP? I didn't see anything on a search
of the lists. My colleague on JSR 168 seems to like this idea, though I am a
little uncomfortable with it in the context of WSRP: I'd prefer much looser
coupling between services be maintained if possible. Aside from that I'd
much prefer that alignment between the two standards be tight enough that,
from the programmers standpoint, location transparency is maintained.
If this hasn't been addressed, are there any thoughts from members of both
standards bodies?
Greg
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
