You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Mark Sztainbok (JIRA)" <ji...@apache.org> on 2014/09/09 02:58:28 UTC
[jira] [Created] (OLINGO-427) Olingo says it using minimalmetadata
when calling a function but then passes metadata causing the service to
return a failure
Mark Sztainbok created OLINGO-427:
-------------------------------------
Summary: Olingo says it using minimalmetadata when calling a function but then passes metadata causing the service to return a failure
Key: OLINGO-427
URL: https://issues.apache.org/jira/browse/OLINGO-427
Project: Olingo
Issue Type: Bug
Components: odata4-client
Affects Versions: V4 4.0.0-beta-01
Reporter: Mark Sztainbok
I'm calling a function on an object and according to the request that is sent to the server the body should contain JSON with minimalmetadata. However Olingo is passing a body with type annotations like it does for fullmetadata which causes the service to return a failure.
The request that Olingo is sending is:
POST https://graph.windows.net/f872e367-02c7-4012-a01c-0f5b7c5636ae/directoryObjects/f0188001-db62-48b1-a97d-0d502658bc62/Microsoft.WindowsAzure.ActiveDirectory.User/DirectoryDataService.assignLicense?api-version=1.21-preview HTTP/1.1
Accept: application/json;odata=fullmetadata
Content-Type: application/json;odata=minimalmetadata
DataServiceVersion: 3.0
MaxDataServiceVersion: 3.0
MinDataServiceVersion: 3.0
Host: graph.windows.net
Connection: Keep-Alive
User-Agent: Apache-Olingo/4.0.0-beta-01-SNAPSHOT
Content-Length: 331
{"addLicenses@odata.type":"Collection(Microsoft.WindowsAzure.ActiveDirectory.AssignedLicense)","addLicenses":[{"odata.type":"Microsoft.WindowsAzure.ActiveDirectory.AssignedLicense","skuId@odata.type":"Edm.Guid","skuId":"6fd2c87f-b296-42f0-b197-1e91e994b900"}],"removeLicenses@odata.type":"Collection(Edm.Guid)","removeLicenses":[]}
and the response from the server is:
HTTP/1.1 400 Bad Request
Cache-Control: private
Content-Type: application/json;odata=fullmetadata;streaming=true;charset=utf-8
Server: Microsoft-IIS/8.0
ocp-aad-diagnostics-server-name: PzLWh4vrtge4c50ALrYodcTq0qh9xPbo2q6QAUmve3c=
request-id: fcff27d2-967b-49ad-a31b-e999c4de4627
client-request-id: 355fda78-28cf-4165-a1c5-45ed82ca6a8a
x-ms-gateway-rewrite: false
x-ms-dirapi-data-contract-version: 1.21-preview
ocp-aad-session-key: gkT6S9eAaU2ALROcR5NJHB7jjd8Wa7eGgLUAHzecQogfg2d1dHXfLgdyzErBsqkBRkQ0H7kOml_esCDYM-BtAF1R7TUnivbJO5TvNjh9KwY.YBQ5e63rWin6S4_wMsUhFMxq_2MTiaQ1C7doIblKWzE
X-Content-Type-Options: nosniff
DataServiceVersion: 3.0;
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
X-Powered-By: ASP.NET
Date: Tue, 09 Sep 2014 00:47:51 GMT
Content-Length: 214
{"odata.error":{"code":"Request_BadRequest","message":{"lang":"en","value":"An OData property annotation was found for a parameter payload; however, parameter payloads do not support OData property annotations."}}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)