Re: [Vote] Release of Apache Olingo OData 5.0.0

+1 On Mon, Nov 27, 2023 at 7:47 AM Grande, Oliver wrote: > +1 > > Hi All, > > This is a vote on first release candidate for Apache Olingo release > version "5.0.0". > This is an upgrade release as it is the first release compatible with Java > 17 and newer, > but incompatible with Java versions

Re: [Vote] RC01 for release of Apache Olingo OData 4.9.0

+1 On Wed, Mar 9, 2022 at 9:59 AM Dave Fisher wrote: > I was going to look today, finally. I see that there are 3 +1 (binding) - > so great. > > > On Mar 6, 2022, at 9:33 PM, mibo wrote: > > > > Hi Dave, > > > >> If this is still active ... > > > > I would say not that active like bigger Apache

Re: [Vote] RC01 for release of Apache Olingo OData 4.8.0

+1 On Fri, Dec 18, 2020 at 12:02 AM mibo wrote: > Hi All, > > I know it is almost holiday season, but would be nice if some of the PMCs > could have a look on this vote. > I still have the hope to provide the 4.8.0 release before Christmas (more > or less as a small present to our community 🙂 ).

Re: [Vote] RC01 for release of Apache Olingo OData 4.7.1

+1 Ramesh.. On Fri, Dec 20, 2019 at 1:06 AM mibo wrote: > Hi All, > > This is a vote on first release candidate (RC01) for Apache Olingo > release version "4.7.1". > The vote will be open for at least 72 hours (planned to close on > Monday 23/12/2019 on 4pm CET or later) and passes if no vote i

Re: [RESULT][VOTE] RC01 for release of Apache Olingo OData 4.7.0

Michael, When will artifacts be pushed to Maven? Ramesh.. On Sun, Dec 1, 2019 at 4:13 PM mibo wrote: > Hi all, > > Again with correct subject ;o) > > The vote passed with three positive and no negative vote. > > The votes are: > +1 Francesco Chicchiriccò (binding) &g

Re: [Vote] RC01 for release of Apache Olingo OData 4.7.0

+1 On Wed, Nov 27, 2019 at 9:42 PM Francesco Chicchiriccò wrote: > On 27/11/19 13:53, mibo wrote: > > Hi All, > > > > This is a vote on first release candidate (RC01) for Apache Olingo > > release version "4.7.0". > > The vote will be open for at least 72 hours (planned to close on > > Saturday

Re: Olingo 4.7

Hi Michael, Just a reminder about the agreed release of Olingo 4.7 by the end of this month. Maybe we can start the build process activities soon. Thank you. Regards Ramesh.. On Tue, Nov 5, 2019 at 10:28 PM Ramesh Reddy wrote: > The end of month works for me. > > Thank you. > >

Re: Olingo 4.7

h? > Is this ok with you? > Or does someone have any objections? > > Kind Regards, Michael > > On Thu, Oct 31, 2019 at 9:08 PM Ramesh Reddy wrote: > > > > Micheal, > > > > It has been more than 5 months since we released 4.6 (May 2019), can we > > co

Olingo 4.7

Micheal, It has been more than 5 months since we released 4.6 (May 2019), can we consider releasing 4.7 in the next couple of weeks? Thank you. Ramesh..

Re: [Vote]Moving olingo library to java 8

+1 Is there any consideration for JDK 11 as JDK 8 is EOL now? On Wed, Sep 4, 2019 at 5:23 AM Rai, Archana wrote: > +1 from me 😊 > > -Original Message- > From: Vasanth, Ramya > Sent: Wednesday, September 4, 2019 1:13 PM > To: dev@olingo.apache.org > Subject: [CAUTION] [Vote]Moving oling

[jira] [Resolved] (OLINGO-1355) Changeset transaction committed on a 400 error code

[ https://issues.apache.org/jira/browse/OLINGO-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy resolved OLINGO-1355. -- Resolution: Fixed changed to >=400 and as far the second point see http://docs.oa

[jira] [Updated] (OLINGO-1355) Changeset transaction committed on a 400 error code

[ https://issues.apache.org/jira/browse/OLINGO-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy updated OLINGO-1355: - Fix Version/s: (Java) V4 4.7.0 > Changeset transaction committed on a 400 error c

[jira] [Resolved] (OLINGO-1386) Refinements to support the apply option

[ https://issues.apache.org/jira/browse/OLINGO-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy resolved OLINGO-1386. -- Resolution: Fixed checked and pulled the PR > Refinements to support the apply opt

[jira] [Updated] (OLINGO-1386) Refinements to support the apply option

[ https://issues.apache.org/jira/browse/OLINGO-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy updated OLINGO-1386: - Fix Version/s: (Java) V4 4.7.0 > Refinements to support the apply opt

[jira] [Updated] (OLINGO-1389) All for post / create of an entity to a navigation

[ https://issues.apache.org/jira/browse/OLINGO-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy updated OLINGO-1389: - Fix Version/s: (Java) V4 4.7.0 > All for post / create of an entity to a navigat

[jira] [Resolved] (OLINGO-1389) All for post / create of an entity to a navigation

[ https://issues.apache.org/jira/browse/OLINGO-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy resolved OLINGO-1389. -- Resolution: Fixed merged the PR > All for post / create of an entity to a navigat

[jira] [Assigned] (OLINGO-1389) All for post / create of an entity to a navigation

[ https://issues.apache.org/jira/browse/OLINGO-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy reassigned OLINGO-1389: Assignee: Ramesh Reddy > All for post / create of an entity to a navigat

[jira] [Assigned] (OLINGO-1386) Refinements to support the apply option

[ https://issues.apache.org/jira/browse/OLINGO-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy reassigned OLINGO-1386: Assignee: Ramesh Reddy > Refinements to support the apply opt

[jira] [Assigned] (OLINGO-1355) Changeset transaction committed on a 400 error code

[ https://issues.apache.org/jira/browse/OLINGO-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy reassigned OLINGO-1355: Assignee: Ramesh Reddy > Changeset transaction committed on a 400 error c

Re: [VOTE] RC01 for 4.6.0 Olingo Release

+1 On Wed, May 1, 2019 at 1:00 AM Francesco Chicchiriccò wrote: > On 2019-05-01 07:24 mibo wrote: > > Hi, > > > > This is a vote on first release candidate (RC01) for next Apache > > Olingo release version "4.6.0". > > The vote will be open for at least 72 hours (it will close on Saturday > > 04

[jira] [Comment Edited] (OLINGO-1350) Update the fasterxml dependencies to newer version

[ https://issues.apache.org/jira/browse/OLINGO-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16830458#comment-16830458 ] Ramesh Reddy edited comment on OLINGO-1350 at 4/30/19 4:4

[jira] [Commented] (OLINGO-1350) Update the fasterxml dependencies to newer version

[ https://issues.apache.org/jira/browse/OLINGO-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16830458#comment-16830458 ] Ramesh Reddy commented on OLINGO-1350: -- [~mibo] I added the changes required

[jira] [Assigned] (OLINGO-1350) Update the fasterxml dependencies to newer version

[ https://issues.apache.org/jira/browse/OLINGO-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy reassigned OLINGO-1350: Assignee: Ramesh Reddy > Update the fasterxml dependencies to newer vers

Re: Olingo 4.6 or 4.5.1

> Will add it when I create the related JIRA issue. > > On Tue, Apr 23, 2019 at 9:59 PM Ramesh Reddy wrote: > > > > We should update the "com.fasterxml.jackson" libraries to latest version > > like 2.9.8, existing versions are old not somewhat sync with late

[jira] [Created] (OLINGO-1350) Update the fasterxml dependencies to newer version

Ramesh Reddy created OLINGO-1350: Summary: Update the fasterxml dependencies to newer version Key: OLINGO-1350 URL: https://issues.apache.org/jira/browse/OLINGO-1350 Project: Olingo Issue

Re: Olingo 4.6 or 4.5.1

to finish last open > issues or to give feedback regarding the release (time). > > Hope this is fine with you. > > Kind regards, Michael > > On Mon, Apr 22, 2019 at 12:13 AM Ramesh Reddy wrote: > > > > Any update on this? > > > > On Sun, Mar 24, 2019 at

Re: Olingo 4.6 or 4.5.1

for a > release by mid/end of April. > > Some more / other opinions? > > Kind regards, Michael > Am 24. März 2019, 15:11 +0100 schrieb Ramesh Reddy : > > Hi, > > > > It has been a while Olingo V4 code base has been released into next > > version, can we do a release of 4.6 or 4.5.1? > > > > Thank you. > > > > Ramesh.. >

Olingo 4.6 or 4.5.1

Hi, It has been a while Olingo V4 code base has been released into next version, can we do a release of 4.6 or 4.5.1? Thank you. Ramesh..

[jira] [Commented] (OLINGO-1345) Annotation based Entity declaration in Olingo 4

[ https://issues.apache.org/jira/browse/OLINGO-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786863#comment-16786863 ] Ramesh Reddy commented on OLINGO-1345: -- No, it is not available in Oling

[jira] [Commented] (OLINGO-1342) Non-json errors not displayed properly in logs

[ https://issues.apache.org/jira/browse/OLINGO-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784811#comment-16784811 ] Ramesh Reddy commented on OLINGO-1342: -- Ok, I see. You are logging the error.

[jira] [Commented] (OLINGO-1342) Non-json errors not displayed properly in logs

[ https://issues.apache.org/jira/browse/OLINGO-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784532#comment-16784532 ] Ramesh Reddy commented on OLINGO-1342: -- I did not understand the patch,

[jira] [Assigned] (OLINGO-1324) A trailing / causes an "Unexpected start of resource-path segment" exception

[ https://issues.apache.org/jira/browse/OLINGO-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy reassigned OLINGO-1324: Assignee: Ramesh Reddy > A trailing / causes an "Unexpected start of resou

Re: FW: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

+1 please put in the request to move. GitHub makes accepting the patches a whole lot simpler. On Mon, Dec 10, 2018 at 3:10 AM Amend, Christian wrote: > Hi Olingo Devs, > > the Git Repository will be moved. If we want to volunteer for the first > wave of relocations we need to react until January

[jira] [Resolved] (OLINGO-1316) multipart/mixed is not allowed as an Accept type with a batch request

[ https://issues.apache.org/jira/browse/OLINGO-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy resolved OLINGO-1316. -- Resolution: Fixed Fix Version/s: 4.6.0 Applied the patch > multipart/mixed is

[jira] [Updated] (OLINGO-1318) Make "loadCoreVocabulary" method in Metadata Parser as "public" method

[ https://issues.apache.org/jira/browse/OLINGO-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy updated OLINGO-1318: - Fix Version/s: (was: (Java) V4 4.5.0) 4.6.0 > Make "loadCoreVo

[jira] [Assigned] (OLINGO-1316) multipart/mixed is not allowed as an Accept type with a batch request

[ https://issues.apache.org/jira/browse/OLINGO-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy reassigned OLINGO-1316: Assignee: Ramesh Reddy > multipart/mixed is not allowed as an Accept type with a ba

[jira] [Resolved] (OLINGO-1318) Make "loadCoreVocabulary" method in Metadata Parser as "public" method

[ https://issues.apache.org/jira/browse/OLINGO-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy resolved OLINGO-1318. -- Resolution: Fixed changed the scope of the method > Make "loadCoreVocabulary&qu

[jira] [Created] (OLINGO-1318) Make "loadCoreVocabulary" method in Metadata Parser as "public" method

Ramesh Reddy created OLINGO-1318: Summary: Make "loadCoreVocabulary" method in Metadata Parser as "public" method Key: OLINGO-1318 URL: https://issues.apache.org/jira/browse/OLINGO-1318

[jira] [Commented] (OLINGO-1302) Performance: Olingo V4 is slower than Olingo V2 when de-serializing JSON response body

[ https://issues.apache.org/jira/browse/OLINGO-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664025#comment-16664025 ] Ramesh Reddy commented on OLINGO-1302: -- [~dswebster] Do want to dig further

[jira] [Commented] (OLINGO-737) Dynamic properties are not serialized

[ https://issues.apache.org/jira/browse/OLINGO-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16663780#comment-16663780 ] Ramesh Reddy commented on OLINGO-737: - AFAIK it has not been implemented. If

[jira] [Commented] (OLINGO-1302) Performance: Olingo V4 is slower than Olingo V2 when de-serializing JSON response body

[ https://issues.apache.org/jira/browse/OLINGO-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16655569#comment-16655569 ] Ramesh Reddy commented on OLINGO-1302: -- As I mentioned they are comple

[jira] [Commented] (OLINGO-1302) Performance: Olingo V4 is slower than Olingo V2 when de-serializing JSON response body

[ https://issues.apache.org/jira/browse/OLINGO-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16655355#comment-16655355 ] Ramesh Reddy commented on OLINGO-1302: -- [~dswebster] JsonDeserializer.popu

[jira] [Commented] (OLINGO-1302) Performance: Olingo V4 is slower than Olingo V2 when de-serializing JSON response body

[ https://issues.apache.org/jira/browse/OLINGO-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16651983#comment-16651983 ] Ramesh Reddy commented on OLINGO-1302: -- [~dswebster] Have you verified

[jira] [Commented] (OLINGO-1303) Serializing OpenType dynamic properties

[ https://issues.apache.org/jira/browse/OLINGO-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16646992#comment-16646992 ] Ramesh Reddy commented on OLINGO-1303: -- IMO for supporting OpenType proper

[jira] [Commented] (OLINGO-1302) Performance: Olingo V4 is ten times slower than Olingo V2 when parsing query response body

[ https://issues.apache.org/jira/browse/OLINGO-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16634660#comment-16634660 ] Ramesh Reddy commented on OLINGO-1302: -- V2 and V4 are completely sepa

[jira] [Assigned] (OLINGO-1299) Guessed type for geospatial in JsonDeserializer defaults to Edm.Geography*

[ https://issues.apache.org/jira/browse/OLINGO-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy reassigned OLINGO-1299: Assignee: Ramesh Reddy > Guessed type for geospatial in JsonDeserializer defaults

[jira] [Created] (OLINGO-1300) Build JSON Metadata Parser in Server Core

Ramesh Reddy created OLINGO-1300: Summary: Build JSON Metadata Parser in Server Core Key: OLINGO-1300 URL: https://issues.apache.org/jira/browse/OLINGO-1300 Project: Olingo Issue Type: New

[jira] [Updated] (OLINGO-1300) Build JSON Metadata Parser in Server Core

[ https://issues.apache.org/jira/browse/OLINGO-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy updated OLINGO-1300: - Description: Currently "server-core-ext" module defines a MetadataParser class to pa

[jira] [Commented] (OLINGO-1295) jackson upgrade odata-server and odata-client

[ https://issues.apache.org/jira/browse/OLINGO-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626290#comment-16626290 ] Ramesh Reddy commented on OLINGO-1295: -- Can you debug and submit a patch why t

[jira] [Resolved] (OLINGO-1293) Srid is not exposed by the MetadataDocument Serializers

[ https://issues.apache.org/jira/browse/OLINGO-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy resolved OLINGO-1293. -- Resolution: Fixed Applied changes with https://git-wip-us.apache.org/repos/asf?p=olingo

[jira] [Resolved] (OLINGO-1292) Json Serialization of geometry value does not allow for an SRID

[ https://issues.apache.org/jira/browse/OLINGO-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy resolved OLINGO-1292. -- Resolution: Fixed Applied the changes with merge https://git-wip-us.apache.org/repos/asf?p

[jira] [Resolved] (OLINGO-1294) Polygon should support multiple interior holes

[ https://issues.apache.org/jira/browse/OLINGO-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy resolved OLINGO-1294. -- Resolution: Fixed Applied the changes to master after review and test checking. https://git

[jira] [Updated] (OLINGO-1293) Srid is not exposed by the MetadataDocument Serializers

[ https://issues.apache.org/jira/browse/OLINGO-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy updated OLINGO-1293: - Fix Version/s: 4.6.0 > Srid is not exposed by the MetadataDocument Serializ

[jira] [Updated] (OLINGO-1294) Polygon should support multiple interior holes

[ https://issues.apache.org/jira/browse/OLINGO-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy updated OLINGO-1294: - Fix Version/s: 4.6.0 > Polygon should support multiple interior ho

[jira] [Updated] (OLINGO-1292) Json Serialization of geometry value does not allow for an SRID

[ https://issues.apache.org/jira/browse/OLINGO-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy updated OLINGO-1292: - Fix Version/s: 4.6.0 > Json Serialization of geometry value does not allow for an S

[jira] [Resolved] (OLINGO-570) Implement OData Json Metadocument Serializer/Parser

[ https://issues.apache.org/jira/browse/OLINGO-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy resolved OLINGO-570. - Resolution: Duplicate > Implement OData Json Metadocument Serializer/Par

[jira] [Assigned] (OLINGO-1292) Json Serialization of geometry value does not allow for an SRID

[ https://issues.apache.org/jira/browse/OLINGO-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy reassigned OLINGO-1292: Assignee: Ramesh Reddy > Json Serialization of geometry value does not allow for an S

[jira] [Assigned] (OLINGO-1293) Srid is not exposed by the MetadataDocument Serializers

[ https://issues.apache.org/jira/browse/OLINGO-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy reassigned OLINGO-1293: Assignee: Ramesh Reddy > Srid is not exposed by the MetadataDocument Serializ

[jira] [Assigned] (OLINGO-1294) Polygon should support multiple interior holes

[ https://issues.apache.org/jira/browse/OLINGO-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy reassigned OLINGO-1294: Assignee: Ramesh Reddy > Polygon should support multiple interior ho

[jira] [Commented] (OLINGO-1246) OData V4: Fixes for Context url when the URL has select clause and expand clause having select

[ https://issues.apache.org/jira/browse/OLINGO-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593827#comment-16593827 ] Ramesh Reddy commented on OLINGO-1246: -- Thank you for quick response [~RalfH

[jira] [Commented] (OLINGO-1246) OData V4: Fixes for Context url when the URL has select clause and expand clause having select

[ https://issues.apache.org/jira/browse/OLINGO-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593786#comment-16593786 ] Ramesh Reddy commented on OLINGO-1246: -- [~RalfHandl] Do you think abov

[jira] [Commented] (OLINGO-1246) OData V4: Fixes for Context url when the URL has select clause and expand clause having select

[ https://issues.apache.org/jira/browse/OLINGO-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586598#comment-16586598 ] Ramesh Reddy commented on OLINGO-1246: -- [~ramya.vasanth] I am trying to use

Re: [VOTE] RC01 for 4.5.0 Olingo Release

+1 for the release On Tue, Aug 7, 2018 at 1:58 PM mibo wrote: > [x] +1 Release this package as Apache Olingo 4.5.0 > > And Thanks to Christian to volunteer as release manager ;o) > > Kind Regards, Michael > > > Am 06.08.2018 um 14:52 schrieb Christian Amend : > > > > Hi, > > > > This is a vote

[jira] [Resolved] (OLINGO-1186) OData 4 parsing older service metadata

[ https://issues.apache.org/jira/browse/OLINGO-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy resolved OLINGO-1186. -- Resolution: Fixed Fixed with commit [https://git-wip-us.apache.org/repos/asf?p=olingo-odata4

[jira] [Updated] (OLINGO-1186) OData 4 parsing older service metadata

[ https://issues.apache.org/jira/browse/OLINGO-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy updated OLINGO-1186: - Fix Version/s: (Java) V4 4.5.0 > OData 4 parsing older service metad

[jira] [Resolved] (OLINGO-1230) OpenType attribute is missing in meta serializer

[ https://issues.apache.org/jira/browse/OLINGO-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy resolved OLINGO-1230. -- Resolution: Fixed [https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h

[jira] [Updated] (OLINGO-1230) OpenType attribute is missing in meta serializer

[ https://issues.apache.org/jira/browse/OLINGO-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy updated OLINGO-1230: - Fix Version/s: (Java) V4 4.5.0 > OpenType attribute is missing in meta seriali

[jira] [Resolved] (OLINGO-1194) EntityResponse's location building doesn't check for unicode strings

[ https://issues.apache.org/jira/browse/OLINGO-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy resolved OLINGO-1194. -- Resolution: Fixed https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h

[jira] [Updated] (OLINGO-1194) EntityResponse's location building doesn't check for unicode strings

[ https://issues.apache.org/jira/browse/OLINGO-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy updated OLINGO-1194: - Fix Version/s: (Java) V4 4.5.0 > EntityResponse's location building doesn't chec

[jira] [Resolved] (OLINGO-1245) Parsing issue with parens

[ https://issues.apache.org/jira/browse/OLINGO-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy resolved OLINGO-1245. -- Resolution: Fixed Resolved with commit  https://git-wip-us.apache.org/repos/asf?p=olingo

[jira] [Updated] (OLINGO-1245) Parsing issue with parens

[ https://issues.apache.org/jira/browse/OLINGO-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy updated OLINGO-1245: - Fix Version/s: (Java) V4 4.5.0 > Parsing issue with par

Re: Olingo server side for Java Standart Edition

Can you explain how you are intending to use Olingo? Olingo does not necessarily favour Java EE, it is built using plain Java SE. For example, you can use Spring to build your Olingo based Web application too. On Tue, Jul 31, 2018 at 11:22 AM Yuri Rusanov wrote: > Hi, > > I'm new in Olingo world

Re: [DISCUSS] New Olingo V4 release

I have a few JIRAs assigned to me which I have been procrastinating to work on, will see if I can get them in before Monday. OLINGO-1245 OLINGO-1230 OLINGO-1194

[jira] [Commented] (OLINGO-1276) Client incorrectly parses stream with left brace in JSON string

[ https://issues.apache.org/jira/browse/OLINGO-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16542208#comment-16542208 ] Ramesh Reddy commented on OLINGO-1276: -- Can you show us testcase per

[jira] [Resolved] (OLINGO-1274) URIParserError gives null response code in response body

[ https://issues.apache.org/jira/browse/OLINGO-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy resolved OLINGO-1274. -- Resolution: Information Provided > URIParserError gives null response code in response b

[jira] [Assigned] (OLINGO-1274) URIParserError gives null response code in response body

[ https://issues.apache.org/jira/browse/OLINGO-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy reassigned OLINGO-1274: Assignee: Ramesh Reddy > URIParserError gives null response code in response b

[jira] [Commented] (OLINGO-1274) URIParserError gives null response code in response body

[ https://issues.apache.org/jira/browse/OLINGO-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538722#comment-16538722 ] Ramesh Reddy commented on OLINGO-1274: -- Here is the relevant verbiage from  O

[jira] [Commented] (OLINGO-1274) URIParserError gives null response code in response body

[ https://issues.apache.org/jira/browse/OLINGO-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16536887#comment-16536887 ] Ramesh Reddy commented on OLINGO-1274: -- [~AarzooAgg] It is considered a user e

[jira] [Commented] (OLINGO-1272) Select without primary key fails with JSON serializer but works fine with XML

[ https://issues.apache.org/jira/browse/OLINGO-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16522288#comment-16522288 ] Ramesh Reddy commented on OLINGO-1272: -- Whether selected or not, since entity&

[jira] [Resolved] (OLINGO-1271) Absolute Context URL with Service Dispatcher

[ https://issues.apache.org/jira/browse/OLINGO-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy resolved OLINGO-1271. -- Resolution: Fixed Fix Version/s: (Java) V4 4.5.0 resolved with commit  https://git-wip

[jira] [Assigned] (OLINGO-1271) Absolute Context URL with Service Dispatcher

[ https://issues.apache.org/jira/browse/OLINGO-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy reassigned OLINGO-1271: Assignee: Ramesh Reddy > Absolute Context URL with Service Dispatc

[jira] [Created] (OLINGO-1271) Absolute Context URL with Service Dispatcher

Ramesh Reddy created OLINGO-1271: Summary: Absolute Context URL with Service Dispatcher Key: OLINGO-1271 URL: https://issues.apache.org/jira/browse/OLINGO-1271 Project: Olingo Issue Type

[jira] [Resolved] (OLINGO-1150) Can't read Decimal value which value bigger than 10M from MicrosoftCRM

[ https://issues.apache.org/jira/browse/OLINGO-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy resolved OLINGO-1150. -- Resolution: Fixed Please see [https://issues.jboss.org/browse/TEIID-5206] for support

[jira] [Resolved] (OLINGO-1252) MetaDataParser will stack overflow when parsing circle references recursively

[ https://issues.apache.org/jira/browse/OLINGO-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy resolved OLINGO-1252. -- Resolution: Fixed Fix Version/s: (Java) V4 4.5.0 Thank you [~rogerc] for the patch

[jira] [Assigned] (OLINGO-1252) MetaDataParser will stack overflow when parsing circle references recursively

[ https://issues.apache.org/jira/browse/OLINGO-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy reassigned OLINGO-1252: Assignee: Ramesh Reddy > MetaDataParser will stack overflow when parsing cir

[jira] [Commented] (OLINGO-1252) MetaDataParser will stack overflow when parsing circle references recursively

[ https://issues.apache.org/jira/browse/OLINGO-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16413882#comment-16413882 ] Ramesh Reddy commented on OLINGO-1252: -- Yes, I understand what you are sayin

[jira] [Commented] (OLINGO-1252) MetaDataParser will stack overflow when parsing circle references recursively

[ https://issues.apache.org/jira/browse/OLINGO-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411191#comment-16411191 ] Ramesh Reddy commented on OLINGO-1252: -- I believe there is text somewhere in

[jira] [Assigned] (OLINGO-1245) Parsing issue with parens

[ https://issues.apache.org/jira/browse/OLINGO-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy reassigned OLINGO-1245: Assignee: Ramesh Reddy > Parsing issue with par

[jira] [Commented] (OLINGO-1226) Serializer to construct metadata document in json format

[ https://issues.apache.org/jira/browse/OLINGO-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16350657#comment-16350657 ] Ramesh Reddy commented on OLINGO-1226: -- Originally captured at OLINGO-570 be

[jira] [Assigned] (OLINGO-1230) OpenType attribute is missing in meta serializer

[ https://issues.apache.org/jira/browse/OLINGO-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy reassigned OLINGO-1230: Assignee: Ramesh Reddy > OpenType attribute is missing in meta seriali

[jira] [Reopened] (OLINGO-1150) Can't read Decimal value which value bigger than 10M from MicrosoftCRM

[ https://issues.apache.org/jira/browse/OLINGO-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy reopened OLINGO-1150: -- The solution provided is incomplete. It does not take into account of validating scale and

[jira] [Resolved] (OLINGO-1150) Can't read Decimal value which value bigger than 10M from MicrosoftCRM

[ https://issues.apache.org/jira/browse/OLINGO-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy resolved OLINGO-1150. -- Resolution: Fixed Fix Version/s: (Java) V4 4.5.0 Accepted and applied the patch that

Re: How to get $count and pagination on the navigational property

1) The $count=true as parameter only advises the service includes the total number of students on the first page of results. It applies to the response entity collection in this case students not just root entity 2) Yes Ramesh.. http://teiid.org On Wed, Jan 10, 2018 at 12:26 PM, Tuo, Erming wro

[jira] [Commented] (OLINGO-1150) Can't read Decimal value which value bigger than 10M from MicrosoftCRM

[ https://issues.apache.org/jira/browse/OLINGO-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16318855#comment-16318855 ] Ramesh Reddy commented on OLINGO-1150: -- Does anyone see any issue with accep

[jira] [Assigned] (OLINGO-1150) Can't read Decimal value which value bigger than 10M from MicrosoftCRM

[ https://issues.apache.org/jira/browse/OLINGO-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy reassigned OLINGO-1150: Assignee: Ramesh Reddy > Can't read Decimal value which value bigger than

Re: partial attribute exposure of single entity model

maybe use $select with above to pair it down in size? On Tue, Nov 28, 2017 at 12:41 PM, Tuo, Erming wrote: > Olingo team, > > > > We currently use Olingo 4.2. Got a question, take the following API > endpoint as example -- /odata/v1/*teachers(‘101’)/students* > > > > Teacher is the main entity h

Re: Olingo V4 EdmxProvider Avaliable?

https://github.com/rareddy/olingo-odata4/blob/master/lib/server-core-ext/src/main/java/org/apache/olingo/server/core/MetadataParser.java an example https://github.com/rareddy/olingo-odata4/blob/master/lib/server-core-ext/src/test/java/org/apache/olingo/server/example/TripPinServiceTest.java Rames

Re: Regarding OData asynchronous service

IMO if you submit a patch with test cases to show the improvement in design and performance then Olingo committers will be open to review. I suggest you start with a JIRA first [1] and detail a bit about your design. This may generate further discussion from where you can submit a patch for your pr

Re: Implementing Olingo V4.4 with JAX-RS/Spring boot

Nikhil, Olingo is built free from dependencies from JAX-RS or Spring Boot. Any integration with those technologies will be on your own implementation, thus there are no documents. Can I ask you what you are trying to use JAX-RS for? Typically one uses JAX-RS to develop a service for which there i

[jira] [Assigned] (OLINGO-1186) OData 4 parsing older service metadata

[ https://issues.apache.org/jira/browse/OLINGO-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Reddy reassigned OLINGO-1186: Assignee: Ramesh Reddy > OData 4 parsing older service metad

  1   2   3   4   5   6   7   >