[jira] [Resolved] (OLINGO-1056) Batch requests/responses on client

[Christian Amend (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OLINGO-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Amend resolved OLINGO-1056.
-
   Resolution: Fixed
 Assignee: Christian Amend
Fix Version/s: V2 2.0.9

Hi,

you can use the EntityProvider.write... methods to transform the objects. then 
you take the input stream and transform it into a String.

If you would like to have a better API you could contribute a patch for this.

Best Regards,
Christian

> Batch requests/responses on client
> --
>
> Key: OLINGO-1056
> URL: https://issues.apache.org/jira/browse/OLINGO-1056
> Project: Olingo
>  Issue Type: Question
>  Components: odata2-core
>Affects Versions: V2 2.0.7
>Reporter: M Carissimi
>Assignee: Christian Amend
> Fix For: V2 2.0.9
>
>
> Hello,
> we have implemented an OData 2 service that supports batch operations. We are 
> now writing an OData client to create a batch request and parse a batch 
> response.
> The body of the batch request needs to be provided as JSON/XML text. Is there 
> an easy way to convert objects (like ODataEntry or ODataFeed) into a JSON/XML 
> string that can be added as the body of our batch request?
> When parsing the response body, is there a way to convert the body text into 
> objects like ODataEntry or ODataFeed?
> Thanks
> Michele



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (OLINGO-1025) Issue in Excel with relative context URI

[Christian Amend (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OLINGO-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Amend resolved OLINGO-1025.
-
   Resolution: Fixed
 Assignee: Christian Amend
Fix Version/s: V2 2.0.9

Hi,

You can use the "serviceRoot(URI)" method in the builder to get absolute URLs.

Best Regards,
Christian

> Issue in Excel with relative context URI
> 
>
> Key: OLINGO-1025
> URL: https://issues.apache.org/jira/browse/OLINGO-1025
> Project: Olingo
>  Issue Type: Bug
>  Components: odata4-server
>Affects Versions: (Java) V4 4.3.0
>Reporter: Olivier VERMONT
>Assignee: Christian Amend
> Fix For: V2 2.0.9
>
>
> Hi Olingo Team,
> I'm trying out your library to publish an odata v4 stream to Excel Power 
> Query.
> I started with your tutorial and ran into this first issue : Excel requires 
> absolute metadata URL in service document which I solved by creating a custom 
> processor as indicated here : https://issues.apache.org/jira/browse/OLINGO-758
> That enabled me to go one step further but I got stuck again when I requested 
> /Products because of the m:context which also seems to be relative : 
> m:context="$metadata#Products"
> I tried playing with the ContextURL but I only managed to come up with this 
> which Excel doesn't like either : m:context="../../../../$metadata#Products 
> Here is the code in the DemoEntityCollectionProcessor.java :
> ContextURL contextUrl = 
> ContextURL.with().entitySet(edmEntitySet).oDataPath(request.getRawBaseUri()).build();
> EntitySerializerOptions options = 
> EntitySerializerOptions.with().contextURL(contextUrl).build();
> Here is the message I get in Excel :
> DataSource.Error: OData : The top level context URL '$metadata#Products' 
> should be an absolute Uri.
> Détails :
> DataSourceKind=OData
> 
> DataSourcePath=http://mydomain.net/Developpement/SettOData.nsf/odata.xsp/Products
> Could anyone please help me to solve this issue ?
> Regards,



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OLINGO-1025) Issue in Excel with relative context URI

[Christian Amend (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OLINGO-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Amend updated OLINGO-1025:

Issue Type: Question  (was: Bug)

> Issue in Excel with relative context URI
> 
>
> Key: OLINGO-1025
> URL: https://issues.apache.org/jira/browse/OLINGO-1025
> Project: Olingo
>  Issue Type: Question
>  Components: odata4-server
>Affects Versions: (Java) V4 4.3.0
>Reporter: Olivier VERMONT
>Assignee: Christian Amend
> Fix For: V2 2.0.9
>
>
> Hi Olingo Team,
> I'm trying out your library to publish an odata v4 stream to Excel Power 
> Query.
> I started with your tutorial and ran into this first issue : Excel requires 
> absolute metadata URL in service document which I solved by creating a custom 
> processor as indicated here : https://issues.apache.org/jira/browse/OLINGO-758
> That enabled me to go one step further but I got stuck again when I requested 
> /Products because of the m:context which also seems to be relative : 
> m:context="$metadata#Products"
> I tried playing with the ContextURL but I only managed to come up with this 
> which Excel doesn't like either : m:context="../../../../$metadata#Products 
> Here is the code in the DemoEntityCollectionProcessor.java :
> ContextURL contextUrl = 
> ContextURL.with().entitySet(edmEntitySet).oDataPath(request.getRawBaseUri()).build();
> EntitySerializerOptions options = 
> EntitySerializerOptions.with().contextURL(contextUrl).build();
> Here is the message I get in Excel :
> DataSource.Error: OData : The top level context URL '$metadata#Products' 
> should be an absolute Uri.
> Détails :
> DataSourceKind=OData
> 
> DataSourcePath=http://mydomain.net/Developpement/SettOData.nsf/odata.xsp/Products
> Could anyone please help me to solve this issue ?
> Regards,



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (OLINGO-1061) POST and PUT for data feed

[Christian Amend (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OLINGO-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Amend resolved OLINGO-1061.
-
   Resolution: Fixed
 Assignee: Christian Amend
Fix Version/s: V2 2.0.9

OData does not allow you to create a collection of entities within one requests.

The closest you can get to this is by sending a batch requests which contains 
each single request for all the entities you want to create.

Best Regards,
Christian

> POST and PUT for data feed
> --
>
> Key: OLINGO-1061
> URL: https://issues.apache.org/jira/browse/OLINGO-1061
> Project: Olingo
>  Issue Type: Question
>  Components: odata2-core
>Affects Versions: V2 2.0.7
>Reporter: M Carissimi
>Assignee: Christian Amend
> Fix For: V2 2.0.9
>
>
> Hello,
> we are writing an application that interfaces with our OData service. Both 
> the consumer and producer sides have been written using Olingo. We need to be 
> able to post/put a collection of entries to be stored atomically. How can 
> this be achieved? 
> The interfaces provided by the Olingo library (EntityProcessor, 
> EntitySetProcessor) only support create, update and delete methods for single 
> entries. Are there equivalent methods for collection of entries?
> Thank you



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (OLINGO-1067) Availability of @odata.type in the response payload

[Christian Amend (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OLINGO-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Amend resolved OLINGO-1067.
-
Resolution: Fixed
  Assignee: Christian Amend

By using odata.metadata=full as parameter which you use to create the 
serializer. But you should not send that manually. You should send back what 
the client requests.

> Availability of @odata.type in the response payload
> ---
>
> Key: OLINGO-1067
> URL: https://issues.apache.org/jira/browse/OLINGO-1067
> Project: Olingo
>  Issue Type: Question
>  Components: odata4-server
>Affects Versions: (Java) V4 4.3.0
>Reporter: VIJAYASIMHA R NAGA
>Assignee: Christian Amend
>
> Currently the Serializer only includes @odata.type in the response payload if 
> the value of Entity is an derived instance of the requested EntityType, is 
> there a way to always include @odata.type in the response payload?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OLINGO-1068) EntityProvider writeEntry does not include inline content in ODataResponse

[Christian Amend (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OLINGO-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Amend updated OLINGO-1068:

Issue Type: Question  (was: Bug)

> EntityProvider writeEntry does not include inline content in ODataResponse
> --
>
> Key: OLINGO-1068
> URL: https://issues.apache.org/jira/browse/OLINGO-1068
> Project: Olingo
>  Issue Type: Question
>  Components: odata2-core
>Affects Versions: V2 2.0.8
>Reporter: M Carissimi
>Assignee: Christian Amend
>
> Hello,
> I have an OData client written using the Olingo library that takes a set of 
> properties (Map) and uses it to put data to a OData server.
> The EntityProvider.writeEntry() method is used to obtain an InputStream for 
> the set of properties to send to the server:
> {code}
>   public ConsumerResponse updateEntry(String anEntitySetName, String 
> anEntryURL, Map someData,
>   String aContentType) throws ConsumerException
>   {
> ConsumerResponse myConsumerResponse = null;
> try
> {
>   EdmEntityContainer myEntityContainer = 
> getMetadata(anEntryURL).getDefaultEntityContainer();
>   EntityProviderWriteProperties myWriteProperties = 
>   EntityProviderWriteProperties.serviceRoot(new 
> URI(extractServiceURIFromURL(anEntryURL))).build();
>   
>   // serialize data into ODataResponse object
>   ODataResponse myResponse = EntityProvider.writeEntry(aContentType, 
>   myEntityContainer.getEntitySet(anEntitySetName), someData, 
> myWriteProperties);
>   // get entity InputStream
>   InputStream myEntity = (InputStream) myResponse.getEntity();
>   
>   // put data to server
>   HttpResponse myHttpResponse = execute(anEntryURL, HTTP_METHOD_PUT, 
> myEntity, aContentType);
> ...
> {code}
> This works well for single entries, but it does not work for entries with 
> inline content. If the set of properties contain both simple properties (e.g: 
> NAME > "MyName") and inline content (e.g. ENTITY_LINK > Map), 
> the ODataResponse object returned by the EntityProvider.writeEntry() method, 
> does not include the inline content.
> I have attempted to set the inline content as an ODataEntry object rather 
> than a Map but the behaviour is the same.
> Why is the inline content not retained by the writeEntry() method?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (OLINGO-1035) Support creating entities with inline URIs to existing entities

[Christian Amend (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OLINGO-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Amend resolved OLINGO-1035.
-
Resolution: Fixed
  Assignee: Christian Amend

Resolved with commit: 
https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=d6f9ddeedb928b32c0ef2f3ea0dbf0ea056b9d3a

Thanks for the patch.

> Support creating entities with inline URIs to existing entities
> ---
>
> Key: OLINGO-1035
> URL: https://issues.apache.org/jira/browse/OLINGO-1035
> Project: Olingo
>  Issue Type: Improvement
>  Components: odata2-annotation
>Affects Versions: V2 2.0.7
>Reporter: Michael Strasser
>Assignee: Christian Amend
>Priority: Minor
> Fix For: V2 2.0.9
>
> Attachments: 
> 0001-OLINGO-1035-Accept-inline-URI-to-create-a-reference-.patch
>
>
> Adding support for posting entities with URI references to other entities.
> For example, given a *Building* posted to {{/Test.svc/Buildings}} with:
> {code:javascript}
> {
>   "Id": "B01",
>   "Name": "Building 1"
> }
> {code}
> it is possible to add a *Room* to {{/Test.svc/Rooms}} with:
> {code:javascript}
> {
>   "Id": "R01-01",
>   "Name": "Room 01",
>   "Building": {
> "__metadata": {
>   "uri": "Buildings('B01')"
> }
>   }
> }
> {code}
> and have the new entity reference the existing one correctly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (OLINGO-1054) Inline Consumer Callback Data handling

[Christian Amend (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OLINGO-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Amend resolved OLINGO-1054.
-
Resolution: Fixed
  Assignee: Christian Amend

Resolved with this commit: 
https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=f24fc8bf42aa225afee2913e47423f11dc9fc237

Thanks for the patch.

> Inline Consumer Callback Data handling
> --
>
> Key: OLINGO-1054
> URL: https://issues.apache.org/jira/browse/OLINGO-1054
> Project: Olingo
>  Issue Type: New Feature
>  Components: odata2-core
>Affects Versions: V2 2.0.6, V2 2.0.7
>Reporter: Ramya
>Assignee: Christian Amend
> Fix For: V2 2.0.9
>
> Attachments: 626b49ed.diff
>
>
> When using the consumer callbacks the data is not part of the result. Yet 
> since there is no access to the parent data the callback can`t decide where 
> to put the data.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)