3

I have to publish my entities(Database tables) via OData service protocol using Java. I thoroughly checked the options on OData implementation and found two major libraries as Apache Olingo and OData4J.

I could't decide which one is best suitable? I could't find any documents on differences between them.

Tunaki
  • 132,869
  • 46
  • 340
  • 423
Trim Bandaru
  • 83
  • 2
  • 8

2 Answers2

2

If you want to use the newest protocol version (v4) you should go with Apache Olingo. There is also SDL OData Framework, but I'm not experienced with this. More info here: http://www.odata.org/libraries/. Apache was taking care of OData since version 2, so I guess that this library is more reliable. On the other hand there are still some open issues in Apache Olingo. Recently the most annoying one from my perspective is: https://issues.apache.org/jira/browse/OLINGO-778

mat3e
  • 781
  • 5
  • 17
  • 1
    I am part of the Olingo community so I am a little biased :) The server part of Olingo V4 is very well maintained. For the client I am missing the time so we are hoping for contributions there. The issue above was fixed btw. – chrisam Dec 17 '15 at 15:28
  • Thanks for all your comments. – Trim Bandaru Dec 18 '15 at 09:56
  • Thanks for fix :) I'm working with Olingo and I've recently started using client. I will check how it works. – mat3e Dec 19 '15 at 09:02
1

We have built an OData service using Olingo with great success. We have used standard Java Objects with Olingo Annotations to expose them as EdmEntities. Olingo supports JPA as well if you want to expose you DB tables directly.

Prior to deciding on Olingo we explored both options and found it very difficult to find substantial documentation on OData4J.

Chaim
  • 58
  • 1
  • 1
  • 5
  • Thanks @Chaim for your reply.I could't able to find best example on olingo with annotations on java POJOs + JPA. would mind to pass on any link that helps me to implement sample project.Thanks – Trim Bandaru Apr 29 '16 at 06:18