Compliance to SCIM 2 section 2.5

[wwebers]

The client SDK seem to incorrectly interprete section 2.5 of the core standard, which states:

When a resource is expressed in JSON format, unassigned attributes, although they are defined in schema, MAY be omitted for compactness.

This "MAY" expresses according to RFC2119 that the server implementation is allowed to either omit the attribute or to send an empty value.

However, when talking to servers which return empty attributes, e.g. empty "display" attributes, we get the infamous UnrecognizedPropertyException exception.

[braveulysses]

@wwebers, can you please provide an example of the problem? Without further information, it seems more likely that you're deserializing with a POJO that doesn't support a "display" field, hence the UnrecognizedPropertyException.

[wwebers]

I'm running a pretty much straight forward request:

    public void getUser() {
        Filter filter = null;
        try {
            filter = Filter.eq("userName", "wwebers");
        } catch (BadRequestException e) {
            e.printStackTrace();
        }
        try {
            ListResponse<UserResource> response = scimService
                    .searchRequest("Users")
                    .filter(filter.toString())
                    .invoke(UserResource.class);
        } catch (ScimException e) {
            e.printStackTrace();
        }
    }

Will say I use the DTOs which are provided by the pingidenity framework. I guess it's also related to my other issue #108