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] Comment on 6.1.4 PortletContext


This sentence strikes me a little bit.
Not the fact that producers need to maintain/persist this information but
rather the explanation "since it is not supplied..."
The reader might ask itself why it isn't supplied and weather this is a
flaw in the spec.
As we talked at the F2F there are reasons why we've chosen to do so.
Can't we restate it to something saying that the portlet handle is the key
for the producer to associate resource allocations for this particular
portlet?

Mit freundlichen Gruessen / best regards,

        Richard Jacob
______________________________________________________
IBM Lab Boeblingen, Germany
Dept.8288, WebSphere Portal Server Development
WSRP Technical Lead
WSRP Standardization
Phone: ++49 7031 16-3469  -  Fax: ++49 7031 16-4888
Email: mailto:richard.jacob@de.ibm.com


                                                                           
             Subbu Allamaraju                                              
             <subbu@bea.com>                                               
                                                                        To 
             05/23/06 11:32 PM         OASIS WSRP TC                       
                                       <wsrp@lists.oasis-open.org>         
                                                                        cc 
                                                                           
                                                                   Subject 
                                       [wsrp] Comment on 6.1.4             
                                       PortletContext                      
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




The new sentence about portletState reads

"Producers choosing to return portletState to the Consumer still need to
persist for themselves any information needed to clean up resources as
the portletState is not supplied on operations informing the Producer
that resources related to the portletHandle can be cleaned up".

I suggest we reword this as

"Producers choosing to return portletState to the Consumer still need to
persist any information needed to clean up portlets. This is needed
since portletState is not supplied with operations such as
destroyPortlets that are used to inform the Producer to cleanup
resources associated with portlets."

Subbu

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





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