[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsrp-interfaces] Questions regarding getPortletDescription()
well, you could always pass a null userContext.
Mit freundlichen Gruessen / best regards,
Richard Jacob
______________________________________________________
IBM Lab Boeblingen, Germany
Dept.8288, WebSphere Portal Server Development
WSRP Standardization Technical Lead
Phone: ++49 7031 16-3469 - Fax: ++49 7031 16-4888
Email: mailto:richard.jacob@de.ibm.com
"Coco,
Christopher"
<Christopher.Coco To
@vignette.com> "Andre Kramer"
<andre.kramer@eu.citrix.com>,
06/07/2004 11:16 "Goldstein, Scott"
PM <Scott.Goldstein@vignette.com>,
"Rich Thompson"
<richt2@us.ibm.com>,
<wsrp-interfaces@lists.oasis-open.o
rg>
cc
Subject
RE: [wsrp-interfaces] Questions
regarding getPortletDescription()
The issue is not calling getPortletDescription() for the cloned portlet. In
the case we are talking
about the Consumer does track the relationship of the CCP to its POP. We
are asking a more base
question of when the Consumer needs to update its metadata on a POP (and
thus all the CCPs based on
that POP), calling to get the entire ServiceDescription of the Producer
just to make sure that the
metadata is "complete", seems a bit heavyweight but necessary as the result
of the getPortletDescription()
method can vary based on the user. Basically, why isn't there a method to
retrieve the "complete"
description for a single POP (irregardless of a user)?
Christopher
-----Original Message-----
From: Andre Kramer [mailto:andre.kramer@eu.citrix.com]
Sent: Monday, June 07, 2004 2:08 AM
To: Coco, Christopher; Goldstein, Scott; Rich Thompson;
wsrp-interfaces@lists.oasis-open.org
Subject: RE: [wsrp-interfaces] Questions regarding
getPortletDescription()
We currently have no requirement for a consumer to call
getPortletDescription() after cloning a POP. This is especially
important for our "clone on write" protocol, so that a consumer can
simply store the returned (new) PortletContext and continue otherwise
unaffected. This in effect makes the meta data of any clone (returned
by getPortletDescription using the new Portlet Handle) equal to that
of the POP (as listed in getServiceDescription).
Therefore, the only use case I can think of for
getPortletDescriptions is for consumers that do not remember portlet
meta data and do not track the relationship of a clones all the way
back to their parent POP. In this case the consumer is not able to
use getServiceDescription and relies on the (same) meta data returned
via getPortletDescription.
By meta data I mean our protocol controls such as groupID and
usesMethodGet. Proprietory info returned could vary (based on user
context) of course.
Regards,
Andre
From: Coco, Christopher [mailto:Christopher.Coco@vignette.com]
Sent: 03 June 2004 01:11
To: Goldstein, Scott; Rich Thompson;
wsrp-interfaces@lists.oasis-open.org
Subject: RE: [wsrp-interfaces] Questions regarding
getPortletDescription()
From my understanding, as long as the call is for a POP as CCPs
aren't listed in the ServiceDescription.
Christopher
-----Original Message-----
From: Goldstein, Scott
Sent: Wednesday, June 02, 2004 5:08 PM
To: Rich Thompson; wsrp-interfaces@lists.oasis-open.org
Subject: RE: [wsrp-interfaces] Questions regarding
getPortletDescription()
Thanks for the info, Rich.
So, just to be completely clear, in the case that the metadata
is not updated in any fashion by the producer, if I were to
call getPortletDescription() with a UserContext containing all
of the Producers' user categories, I would be guaranteed to
receive the same structure as if I had called
getServiceDescription(). Correct?
Scott
From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent: Wednesday, June 02, 2004 8:57 AM
To: wsrp-interfaces@lists.oasis-open.org
Subject: Re: [wsrp-interfaces] Questions regarding
getPortletDescription()
Thanks for your persistence ... sometimes as we get busy
we hope that others will supply the answers :}
The data in GetPortletDescriptionResponse is the same
that is included in the array returned by
getServiceDescription() with a few caveats. The data is
allowed to change (portlet data updated, user access
rights, etc) and most Producers will only return data
from getServiceDescription() for their POPs while
getPortletDescription() can be invoked against any
portletHandle.
Rich
"Goldstein, Scott"
<Scott.Goldstein@vignette.com>
To
06/02/2004 11:31 AM <wsrp-interfaces@lists.oa
sis-open.org>
cc
Subject
[wsrp-interfaces]
Questions regarding
getPortletDescription()
I haven't received a reply to my message I sent out last
week, so I thought I would try to resend it. If you have
any answers to the questions below, please reply.
Thanks.
I have the following questions regarding the
getPortletDescription() operation:
1. How does the data returned in the
PortletDescriptionResponse relate to the portlet
description contained within the ServiceDescription?
Must they be identical? Or, can the producer change the
data based on the user context. For instance, could the
producer not specify a particular supported mode if the
user is not an admin?
2. If the answer to #1 is that they can be
different, then is there a way to ensure, when calling
this method, that the PortletDescription returned would
be equal to that in the ServiceDescription? Perhaps by
sending all of the possible User Categories?
3. If the answer to #1 is that they must be the
same, then is the only use of the UserContext attribute
to allow the producer to throw an AccessDenied Fault?
Will passing all user categories avoid this?
Essentially, I'm trying to understand the intended use of
getPortletDescription() and if it can be used as an
optimization to update portlet meta data without having
to retrieve the full service description.
Thanks for the information.
Scott
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]