RE: [wsrp] Portlet lifecycles and CCP's

[Andre Kramer <andre.kramer@eu.citrix.com>]

Title: RE: [wsrp] Portlet lifecycles and CCP's

It's a small point, but some systems may wish to archive customizations rather than delete them but the main trust is that the consumer can no longer rely on them being accessible (causing InvalidHandle faults).

Regards,
Andre

-----Original Message-----
From: Subbu Allamaraju [mailto:subbu@bea.com]
Sent: 08 June 2004 14:42
To: wsrp@lists.oasis-open.org
Subject: Re: [wsrp] Portlet lifecycles and CCP's

>>
>>>"cloneBeforeWrite" portlet instances get cleaned up?
>>
>>Consumer may call destroyPortlets to clean those clones. If registration
>>is required, the Producer will destroy cloned portlets during
>>deregistration.
>
>
> we don't say that in the spec.
> Again, a Consumer must call destroyPortlets() to release resources, first.

The spec does require this indirectly. All handles created within a
registrationContext are required to become invalid after deregister().
This means that all cloned portlets become invalid even without the
Consumer calling destroyPortlets() first. From the consumer's
perspective, those CCPs no longer exist after deregister().

Subbu

To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsrp/members/leave_workgroup.php.