I agree that this is one of questions raised by WSRP users, but there
are few issues to be considered here.
a. Most of the times, consumer users cannot act upon these events at
production time. The only time these events make sense is during design
time. At production time, such notifications just add more traffic.
b. We should also consider if such updates can be notified via a
registry (e.g. via UDDI 3.0 notifications).
Regards,
Subbu
Rich Thompson wrote:
>
> I was reminded this AM of a couple of possible events we have discussed
> in the past:
>
> *ProducerMetadataChanged* - Notification that the Producer's metadata
> has changed. The Consumer may want to refresh its cached info.
> *PortletMetadataChanged* - Notification that the Portlet's metadata has
> changed. The Consumer may want to refresh its cached info.
> *AvailablePortletsChanged* - Notification that the Producer has changed
> the set of portlets exposed via WSRP. Event payload should indicate the
> type of change (added, deprecated, deleted), the portletHandle of the
> subject portlet and the portlet's title.
>
> Rich
