Re: [wsrp-interfaces] Questions regarding getPortletDescription()

[Rich Thompson <richt2@us.ibm.com>]

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>

06/02/2004 11:31 AM

To	<wsrp-interfaces@lists.oasis-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