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

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp-wsia message

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


Subject: RE: [wsrp-wsia] [change request #201] PortletDescription applies toclones


I do not think we have such a statement currently. 

Rich Thompson




Andre Kramer <andre.kramer@eu.citrix.com>
03/04/2003 11:20 AM
 
        To:     wsrp-wsia@lists.oasis-open.org
        cc: 
        Subject:        RE: [wsrp-wsia] [change request #201] 
PortletDescription applies      to clones


I was only trying to constrain a clone on write. Actually, I don't care
strongly about clonePortlet() but at least consumers are able to call
getPortletDescription() as it is in the same factor. I can image a public
offered portlet is always non-secure but its clone wants
defaultMarkupSecure. Do we currently have a statement about clone and the
clone's portlet description?

regards,
Andre
-----Original Message-----
From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent: 04 March 2003 16:00
To: wsrp-wsia@lists.oasis-open.org
Subject: Re: [wsrp-wsia] [change request #201] PortletDescription
applies to clones


A couple of comments:

1. I would find it weird for any cloned Portlet to not share the 
PortletDescription of the source for the clone. Is there a use case for 
them not sharing this metadata?
2. I would not want to introduce a difference between clones that depends 
on the method by which the clone was produced. This seems to add 
complexity without value.

Rich Thompson




Rich Thompson/Watson/IBM@IBMUS
03/04/2003 10:19 AM
 
        To:     wsrp-wsia@lists.oasis-open.org
        cc: 
        Subject:        [wsrp-wsia] [change request #201] 
PortletDescription applies to clones


Document: Spec
Section: 5.1.11 and 6.3.3
Page/Line: 21/29
New text: When a producer clones a portlet, using the lazy mechanism 
described in section 6.3.3., the following values MUST be the same as the 
original portlet's description: markupTypes[]; groupID; userCategories[]; 
userProfileItems[]; usesMethodGet; defaultMarkupSecure; 
userContextStoredInSession; templatesStoredInSession; 
hasUserSpecificState; doesURLtemplateProcessing. Portlets explicitly 
created via createPortlet() do not have this restriction (call 
getPortletDescription() after clone()).

Reason: getPortletDescription is in the (optional) portlet management not 
the (required) serviceDescription factor. We could move it and force a 
consumer call to getPortletDescription().

----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>



----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>

----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>



----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>




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