grouper-users - retrieveSubjectDetail versus ws.subject.result.attribute.names
Subject: Grouper Users - Open Discussion List
List archive
- From: Colin Hudler <>
- To: "" <>
- Subject: retrieveSubjectDetail versus ws.subject.result.attribute.names
- Date: Fri, 16 Apr 2010 13:44:20 -0500
Hi,
I was just wondering, when using retrieveSubjectDetail=F, why does it still retrieve the attributes specified in "ws.subject.result.attribute.names" of grouper-ws.properties.
Specifically I am wondering why this property overrides the client request to not include details. I suspect it is a semantic difference. Details could be those attributes other than the subjectId (a mistaken assumption), or the reality in the code; that details are only those things specified by "ws.subject.result.detail.attribute.names".
I confirmed this in
util/GrouperServiceUtils.java: calculateSubjectAttributes()
On further reflection of the differences, please just consider this email a comment on the documentation, so it is not a total loss.
From grouper-ws.properties:
# subject attribute names to send back when a WsSubjectResult is sent, comma separated
# e.g. name, netid
# default is none
ws.subject.result.attribute.names =
One must infer that the client cannot request not to receive the attributes specified here.
- retrieveSubjectDetail versus ws.subject.result.attribute.names, Colin Hudler, 04/16/2010
- RE: [grouper-users] retrieveSubjectDetail versus ws.subject.result.attribute.names, Chris Hyzer, 04/16/2010
Archive powered by MHonArc 2.6.16.