OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [wsrp] Portlet lifecycles and CCP's






Subbu Allamaraju <subbu@bea.com> wrote on 06/08/2004 05:26:38 AM:

> Some differences between a POP and CCP:
>
> a. POPs are offered by the producer, while CCPs are created subsequently
> either due to an implicit cloning during performBlockingInteraction or
> an explicit cloning via the portlet management interface.
>
> b. CCPs may have some persistent user/consumer specific state
> associated. POPs cannot have user/consumer specific state.
>
> c. CCPs cannot exist if the Producer does not offer the portlet
> management interface.
>
> d. If registration is required, CCPs are scoped to a registration.
> Producer destroys CCPs at the end of the regitration.

yes (a wise Producer would do that) but the Consumer must call
destroyPortlets()
if he doesn't need them any more (even if he will deregister afterwards)
according to the contract.

> Yes, it is not an error for the consumer to send cloneBeforeWrite even
> when the Producer does not offer the portlet management interface.
>
> > "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.

Richard



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]