EclipseLink/Development/JPA-RS

EclipseLink JPA-RS Development

The EclipseLink 2.4.0 release introduced JPA-RS allowing developers to easily expose persistence units over REST (JAX-RS). The intent was to allow clients (HTML5/JS, Mobile, JavaSE/JavaFX) to easily access persistent data over REST with JSON or XML. This page tracks the ongoing feature development of JPA-RS including planned features for upcoming releases as well as a back-log of future enhancements. The details of each item will be tracked within its bug and associated wiki pages or documents.

Planned Features

Bug	Issue	Description	Target Release
bug 387313	PUT/POST	Cannot create an entity containing other nested entities, using JPA-RS with static PU	?

Proposed Features

Bug	Issue	Description
?	Config File	Add an optional XML configuration which when provided controls which persistence units are made available through JPA_RS and what operations within each persistence unit are made available. This configuration file will also control extended functionality where any existing or custom JPA-RS operation can have a custom handler specified or a handler can be specified to intercept all operations or all unsupported requests.
bug 387218	Pagination	Support pagination (count, first, max, getNext<N>) using URI query parameters.
?	Partial Entities	Add support for clients being able to request partial entities and graphs that will reduce the payload size or reduce the number of requests required to retrieve and to pass back an entity graph.
?	Detailed error response	Add support for clients being able to get more information in an error response. Please note that this is an addition to the HTTP error/status code that is currently being returned in response. The JPA-RS would return an error message in the body of the response that would contain an (EclipseLink specific) error code and description. As an example, an error response would look like : [ "code":"1245", "description":"invalid query" ]