Skip to main content

OReva - Fork of OData4J library

Teiid community depends upon OData4J for its V2 implementation of the OData protocol. We see that there has been not much activity in OData4J project for last 2 years, so we consider this is project is effectively dead by all means. However, Teiid community still on hook to support our OData V2 implementation for little while longer (I see at least 2 yrs), for that reason we have forked this project and calling it "OREVA".

I have somewhat simplified the offering by removing the JDBC and JPA as we do not use those modules, but rest of core protocol is intact. We will try to keep it up with any bug fixes and maintenance. So, if you are wanting to submit a patch or work on some enhancements you can always come and talk to us,  patches are Welcome.

Here is the fork https://github.com/teiid/oreva   If there is enough interest form OData4J remaining community, I do not mind moving this to different GitHub organization other than Teiid. If you find a issue, use https://github.com/teiid/oreva/issues  for now we are using Teiid's issues system.

I also would like to thank John Spurlock for his all his contributions towards OData4J, Thank you. It is a very good OData framework

Thank you.

Ramesh..
http://teiid.org

Comments

  1. It's nice of you to continue working on it.

    Have you proposed to John Spurlock of taking over the odata4j project? That way you'll simply create a new version... and less confusion for the community.

    Thanks!

    ReplyDelete
  2. This comment has been removed by a blog administrator.

    ReplyDelete
  3. No. As I mentioned, this came out our necessity to support the library for Teiid project. Right now, I do not have any aspirations without broader community support to take beyond V2, as most of my time goes to supporting Teiid project. I am also a commiter on Apache Olingo for V4. Even though this may look like I am trying to segment the OData4J community that not all my intentions. I wanted to start something new that I can manage the way from what I learned from Teiid, may that be tools, infrastructure etc need to a run a project that I am comfortable and have control over it.

    I just heard from one of Teiid community member that, they are going to contribute to OData V3 version to OReva, that is a great news for us. I hop I can keep the momentum up.

    ReplyDelete
  4. And also do not forget, I removed the JPA and JDBC interfaces from the library, IMO they do not belong core library, they need to be sub-projects. I know JPA is popular with lot of community members, but in itself is lot of work to maintain.

    ReplyDelete

Post a Comment

Popular posts from this blog

Teiid Spring Boot 1.7.0 Released

Teiid Spring Boot version 1.7.0 to support Teiid 16.0 has been released. This release is mainly to support the Teiid's latest version.  In this release, the support for OpenAPI code generation based on VDB has been removed as there is no community interest and moreover it was at OpenAPI 2.0, and the industry has moved to 3.0 and beyond. There are no plans to further pursue this feature. VDB maven plugin was also removed, which was intended to be a replacement for the VDB importing feature was to be used when working on OpenShift, however, since it requires the Maven repository and does not completely represent the feature as defined on the WildFly based deployments this is also removed. You can still use the VDB import feature with Teiid Spring Boot, simply define the VDB with your "IMPORT DATABASE" statements and provide the additional files along with the main VDB file. During the start of the application, Teiid Spring Boot will load all the necessary DDL files for the ...

Teiid Spring Boot 1.5.0 Released

I am excited to announce that Teiid Spring Boot version 1.5.0 released today to the maven repository based on Teiid 14.0.0 release. If you have not used Teiid Spring Boot before, it is built on top Teiid Core libraries with developer simplification in mind. It simplifies the deployment model to a single VDB and provides you with executable binary rather than Server like WildFly where you need to deploy your VDBs. The release highlights are * Cassandra Data Source support * Materialization automation * Spring Boot version to 2.2.6 * Keystore/Truststore simplifications that work across the system * SOAP Data Source support * FTP Database Support * A Lot of changes to detect data sources based on their inclusion as dependencies and consistent naming schemes across both Teiid and Teiid Spring Boot. For a full list see this Take look at the various examples in Teiid Spring Boot and take it for test drive let me know if there are any issues or improvements you see. Ramesh...

Teiid Designer 8.3 Beta 1 milestone available

Teiid Designer 8.3 , targeted for release late next month, is focused on bug fixing and improving the integration of the JBoss server and Teiid runtime frameworks. We've released our first milestone, 8.3 Beta1 and it's available from our downloads page via zip archive or update site . Highlights include... Addressed problems re-deploying non-JDBC data sources TEIIDDES-1742 and TEIIDDES-1767   Improved Teiid Configuration tree behavior TEIIDDES-1730 - Add Create Teiid VDB Data Source action to VDB selection TEIIDDES-1835 - Add preview artifact management actions TEIIDDES-1847 - Filter preview artifacts in tree if not tied to current runtime user      TEIIDDES-1814 - Remove Teiid-specific server creation dialog Teiid Designer Team