Grouper Users - Open Discussion List

[Scott Koranda <>]

Hi,

On Thu, Sep 13, 2012 at 8:45 AM, Chris Hyzer 
<>
 wrote:
> Yeah, that is the way it was implemented, I updated the docs.

Thanks.

> I can see how what you expect is better, though the way it is implemented 
> there is no way in the underlying logic to differentiate between a blank 
> description sent in, and no description sent in...

No problem. I just wanted to make sure I understood.

Thanks,

Scott

>
> Chris
>
> -----Original Message-----
> From: 
> 
>  
> [mailto:]
>  On Behalf Of Scott Koranda
> Sent: Thursday, September 13, 2012 8:53 AM
> To: grouper-users
> Subject: [grouper-users] Group Save Lite WS with update sets description to 
> empty string
>
> Hi,
>
> I am using Grouper WS from Grouper 2.1.2.
>
> I sent this JSON in via a POST
>
> {
>    "WsRestGroupSaveLiteRequest":{
>       "actAsSubjectId":"GrouperSystem",
>       "saveMode":"UPDATE",
>       "groupName":"Reference:COmanageDataSource:LIGO 
> Laboratory:AdLIGOProject2",
>    }
> }
>
> to the URL
>
> https://127.0.0.1/grouper-system/servicesRest/v2_1_000/groups/Reference%3ACOmanageDataSource%3ALIGO+Laboratory%3AAdLIGOProject
>
> and the name of the group changed from 'AdLIGOProject' to 'AdLIGOProject2' 
> as I expected.
>
> The description for the group, however, which had previsouly
> been set was unset or set to an empty string. I did not expect
> that.
>
> Is the defined behavior that when not specified in the input
> JSON the description is set to a null or empty string?
>
> Thanks,
>
> Scott