Re: [wsrp] import/export on producer offered portlets

[Subbu Allamaraju <subbu@bea.com>]

Here is my summary of today's discussion on this topic:

a. It is valid for the consumer to
    i. send all portlet handles, whether producer offered or not in an 
exportPortlets request.
    ii. exclude producer offered portlet handles from the exportPortlets 
  request

The consumer also needs to consistently adopt the same approach during 
importPortlets (i.e exclude or include POPs in both cases)

b. On an importPortlets response, the consumer must be willing to accept 
both POP handles and CCP handles. importPortlets does not mean that a 
clone has taken place.

c. The consumer must also be prepared to detect whether it received POP 
handles or CCP handles in the importPortlets response.

Did I miss anything?

Subbu


Subbu Allamaraju wrote:
> Thinking further, there is an additional possibility. If a producer 
> wants to let producer-offered portlet state be always determined 
> statically (e.g. by a portlet container), it can encode those semantics 
> in the export data but not actually encode any state. I guess it is 
> implementation specific.
> 
> Subbu
> 
> Rich Thompson wrote:
>>
>> Since there is no reason to expect the importing Producer to have the 
>> same configuration as a POP, I would argue the preferred 
>> implementation will export it in the same manner as a CCP.
>>
>> Rich
>>
>>
>> *Subbu Allamaraju <subbu@bea.com>*
>>
>> 12/13/2006 12:11 PM
>>
>>     
>> To
>>     OASIS WSRP TC <wsrp@lists.oasis-open.org>
>> cc
>>     
>> Subject
>>     [wsrp] import/export on producer offered portlets
>>
>>
>>     
>>
>>
>>
>>
>>
>> What is the expected behavior when a consumer includes a producer
>> offered portletHandle in the exportPortlets request?
>>
>> Fail the export for that portlet, or not return any state?
>>
>> Subbu
>> _______________________________________________________________________
>> Notice:  This email message, together with any attachments, may contain
>> information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
>> entities,  that may be confidential,  proprietary,  copyrighted  and/or
>> legally privileged, and is intended solely for the use of the individual
>> or entity named in this message. If you are not the intended recipient,
>> and have received this message in error, please immediately return this
>> by email and then delete it.
>>
> 
> _______________________________________________________________________
> Notice:  This email message, together with any attachments, may contain
> information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
> entities,  that may be confidential,  proprietary,  copyrighted  and/or
> legally privileged, and is intended solely for the use of the individual
> or entity named in this message. If you are not the intended recipient,
> and have received this message in error, please immediately return this
> by email and then delete it.

_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.