At the current state the JPA Processor provide support for:
- Generating OData metadata from JPA metadata.
- Processing Get requests by converting them into Criteria Builder queries.
- Supporting entity manipulations.
More details can be found in the Tutorials.
The JPA Processor requires, others than Olingo, minimum Java version 1.8. The current version comes with Olingo 4.6.0. If later versions of Olingo are available this may change.
Even so no JPA implementation is preferred, as long as it supports JSR-338 Java Persistence 2.1, it has to be stated that all test have been performed with Eclipselink 2.7.1. If you have any problem e.g. with Hibernate create an issue, but there is no guaranty that it can be solved, as Hibernate implements some JPA interfaces "differently" than EclipseLink.
Download and Installation
The JPA Processor is a collection of Maven projects. To use it you need to clone the repository, import the projects and declare a dependency to either the metadata generation only:
<dependency> <groupId>com.sap.olingo</groupId> <artifactId>odata-jpa-metadata</artifactId> <version>0.3.6-SNAPSHOT</version> </dependency>
Or to the complete processor:
<dependency> <groupId>com.sap.olingo</groupId> <artifactId>odata-jpa-processor</artifactId> <version>0.3.6-SNAPSHOT</version> </dependency>
The project is still in the state of incubation, so some incompatible changes my come up, see To-Do. Nevertheless feel free to use the JPA processor where ever it helps.
How to obtain support
For bugs, questions and ideas for enhancement please open an issue in github.
The flowing extensions/changes are planned:
- Transient fields
- Enable hooks for retrieving data
- Support of $ref
- ETag on $metadata
- Support asynchronous requests
- Parallel processing for $expand
- Enable server side paging at $expand
- Overload Operations
Copyright (c) 2017 SAP SE or an SAP affiliate company. All rights reserved. This file is licensed under the Apache Software License, v.2 except as noted otherwise in the License file.
|0.2.4||- Switch to Olingo version 4.4.0
- Support of Enumeration Types
- Support of $count at $expand
|0.2.6||- Solution for issue #21
- JPA Join tables can be used e.g. for Many To Many relationship (issue #22). If such relation shall be used in a filter a corresponding JPA entity is required, which can be hidden from the API using @EdmIgnore. Please be aware that in case both source and target are subtypes Eclipselink (version 2.7.1 used) may get confused when generating a subquery for filtering, see Bug 529565
|0.2.7||- Solution for issue #29
- Solution for issue #35
- Solution for issue #37
|0.2.8||- Support of Collection Properties
- New tutorials 1.7 Suppressing Elements and 1.13 Collection Properties
|0.2.9||- Support on top level server driven paging
- New tutorial 4.3 Server Driven Paging
|0.2.10||- Handling of Content-Id in batch requests
- Update to Olingo 4.5.0
- Update tutorial 1.6, 3.3, 3.5 and 3.6
|0.3.1||- Support of instance based authorizations
- Solution for issue #60
- Solution for issue #49
- Correct typo in interface JPAODataPagingProvider
- New tutorials 2.3, 4.4
|0.3.2||- Lift unit tests to JUnit 5
- Correction of http return codes on empty responses
|0.3.3||- Support of PUT requests on collection properties and simple primitive properties
- Update to Olingo 4.6.0
- Solution for issue #69
- Solution for issue #71
- Update tutorial 4.4
|0.3.4||- Support of $select as part of $expand
- Support of field groups
- Introduction of a request context, which includes deprecation of methods
- Etag now written into response e.g. @odata.etag when JSON was requested
- Solution for issue #78
- Updated tutorials: 2.2, 2.3, 3.1, 3.2, 4.4
|0.3.5||- Extension of session context, so an entity manager factory can be provided. This will allow creating Spring based services without
- Solution for issue #85
- Usage of Olingo JSON deserializer for CUD requests
- Extension of session context, so an non Edm Name Builder can be provided
|0.3.6||- Enable more flexible transaction handling
- Part solution for issue #83
- Increase support of Spring by performing request mapping in case a mapping path is provided via the service context