Re: [wsrp] Portlet lifecycles and CCP's

[Subbu Allamaraju <subbu@bea.com>]

Hi Ricky,

Some comments inline.

Subbu

ricky_frost@peoplesoft.com wrote:

> 
> 
> 
> I've been trying to understand the relationship between POP's and CCP's and
> the Portlet lifecycle. It appears that before a blockingInteraction can be

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.

> successful a portlet must be consumer-configured. This happens by one of
> two ways. Either by first calling the optional Management clonePortlet, or
> by requesting cloneBeforeWrite on the blockingInteraction itself. So it
> seems that a Producer not offering a Management option might still allow
> the cloneBeforeWrite request. My question: how then will these

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.

> While searching for an answer I came across section 8 of the 1.0
> specification where there is a reference to "releasePortlet" as follows:
> 
> Any Producer that supports cloning portlets on performBlockingInteraction()
> MUST support the releasePortlet() operation.

> 
> Can someone explain this? There are no other references in the document...
> Ricky Frost
> 
> 
> 
> 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.
>