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

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp-interfaces message

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


Subject: RE: [wsrp-interfaces] Groups - Getting Portlet Description - Proposal.docuploaded


Title: RE: [wsrp-interfaces] Groups - Getting Portlet Description - Proposal.docuploaded

A producer can offer both 1.0 and 2.0 interfaces externally to keep users happy. For re-factored operations, these can tie back to one internal interface.

I don't object to increasing the flexibility of getServiceDescription() but do not wish getPortletDescription() to be ignored. Once we have fuller registry support, then query type use cases should really be supported by the registry, leaving only getPortletDescription() for filling in non-published portlet meta data.

Regards,
Andre

-----Original Message-----
From: Subbu Allamaraju [mailto:subbu@bea.com]
Sent: 22 July 2004 15:27
To: wsrp-interfaces@lists.oasis-open.org
Subject: Re: [wsrp-interfaces] Groups - Getting Portlet Description - Proposal.docuploaded

Refactoring, if allowed, would address the use case. But, IMO, dropping
an operation from one interface and moving it to another may not be
acceptable to the spec users.

Subbu

Andre Kramer wrote:

> We would not be dropping it but re-factoring (moving operations to other
> Interfaces)! Presumably properties would be subsumed by WS Resource
> Framework too. That might leave getPortletDescription() in an interface
> named PortletManagement on its own ...
>

>
> Regards,
>
> Andre
>

>
> ------------------------------------------------------------------------
>
> *From:* Rich Thompson [mailto:richt2@us.ibm.com]
> *Sent:* 22 July 2004 13:24
> *To:* wsrp-interfaces@lists.oasis-open.org
> *Subject:* RE: [wsrp-interfaces] Groups - Getting Portlet Description -
> Prop osal.docuploaded
>

>
>
> If we choose to leverage WSRF, we can drop the destroyPortlets()
> operation in favor of the WSRF-RL destruction semantics (both immediate
> and timed).
>
> Rich
>
> *Andre Kramer <andre.kramer@eu.citrix.com>*
>
> 07/22/2004 07:06 AM
>
>      
>
> To
>
>      
>
> "'subbu@bea.com'" <subbu@bea.com>, wsrp-interfaces@lists.oasis-open.org
>
> cc
>
>      
>

>
> Subject
>
>      
>
> RE: [wsrp-interfaces] Groups - Getting Portlet Description - Prop      
>  osal.doc uploaded
>

>

>
>      
>

>
>
>
>
> I've never liked having destroyPortlets() (required for cloning) and
> get/setPortletProperties() in the same interface. Maybe we could
> re-factor these along with getPortletDescription()?
>
> Regards,
> Andre
>
> -----Original Message-----
> From: subbu@bea.com [mailto:subbu@bea.com]
> Sent: 19 July 2004 16:24
> To: wsrp-interfaces@lists.oasis-open.org
> Subject: [wsrp-interfaces] Groups - Getting Portlet Description -
> Proposal.doc uploaded
>
> The document Getting Portlet Description - Proposal.doc has been
> submitted by Subbu Allamaruaju (subbu@bea.com) to the WSRP Interfaces SC
> document repository.
>
> Document Description:
>
> Download Document:  _
> _http://www.oasis-open.org/apps/org/workgroup/wsrp-interfaces/download.php/7819/Getting%20Portlet%20Description%20-%20Proposal.doc

>
>
> View Document Details: _
> _http://www.oasis-open.org/apps/org/workgroup/wsrp-interfaces/document.php?document_id=7819
>
>
> PLEASE NOTE:  If the above links do not work for you, your email
> application
> may be breaking the link into two pieces.  You may be able to copy and
> paste
> the entire link address into the address field of your web browser.
>



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