RE: [wsrp] How to destroy portlets with consumer stored portletState?

["Ramaswamy, Satish" <skr@vignette.com>]

Agreed. The destroyPortlets should include this information.
Our implementation sends only the portlet handle. 

Satish

-----Original Message-----
From: Subbu Allamaraju [mailto:subbu@bea.com] 
Sent: Thursday, April 27, 2006 7:53 AM
To: WSRP TC
Subject: Re: [wsrp] How to destroy portlets with consumer stored
portletState?

Good use case. I agree that destroyPortlets should include this
information.

Since some producers now require portletState to be managed by 
consumers, can TC members from those implementations comment on how they

  support this use case currently?

Subu

Stefan Hepper wrote:
> I would like to solve the following use case:
> - portlet returns portletState in order to have this state stored on
the 
> consumer
> - part of this state contains the server address where the portlets
gets 
> the email and calendar information
> - now the portlet is destroyed and would like to clean up the entries
on 
> the server, however, the destroy call does not provide the
portletState, 
> but only the portletHandle
> 
> How is this use case supposed to work? Wouldn't you need either a 
> portletState array in the destroy or exchange the portletHandle with 
> portletContext?
> 
> 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


---------------------------------------------------------------------
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