Re: [wsrp] Public review comment: allowing the portlet to receive newevents

[Rich Thompson <richt2@us.ibm.com>]

Discussions within the Coordination
SC decided to try and steer clear of a dynamic pub/sub model while also
accommodating some dynamic character to the set of events related to a
Portlet. The general hope was that one of the eventing specifications (WS-Notification
or WS-Eventing) would become a standard adopted in the marketplace in a
timely manner such that this use case would be solved by a wsrp:PortletDescriptionModified
event delivered through such an asynchronous mechanism. Considering where
we are in the process, it would be good to look at that decision again.

To help start this review, a quick look
at status says that WSN is about to be submitted for review by the OASIS
membership. WS-Eventing was contributed to W3C in March, 2006.

Rich

Stefan Hepper <sthepper@hursley.ibm.com>

07/25/2006 02:02 AM

To	WSRP TC <wsrp@lists.oasis-open.org>
cc
Subject	[wsrp] Public review comment: allowing the portlet to receive new events

The current WSRP draft has an asymmetry for events
that are not declared 
in the portlet description:
It can publish new events at runtime by just returning the new event, 
but it cannot register itself for receiving new events at runtime.

Use case:
A generic Atom feed portlet that wants to publish specific events based
on the feed. E.g. if it points to a feed that provides new published 
books it would like to publish an event with author name and book title
for the current selected book entry.

Proposal:
In PortletContext add
[O] EventDescription handledEvents[]
[O] QName unhandledEvents[]

Handled events will be treated as events that the portlet accepts to 
handle form this point on. Unhandled (better name suggestions?) events
are events that the portlet no longer handles. If unhandled events are
sent to the portlet they will be ignored.

Stefan


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs
in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php