Jump to: navigation, search

Difference between revisions of "EclipseLink/Development/JPA-RS"

(New page: __NOTOC__ = 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 a...)
 
Line 20: Line 20:
 
{|{{BMTableStyle}}
 
{|{{BMTableStyle}}
 
|-{{BMTHStyle}}
 
|-{{BMTHStyle}}
 +
! Bug
 
! Issue
 
! Issue
 
! Description
 
! Description
 
|-
 
|-
| Pagination || Support pagination (count, first, max) using URI query parameters.
+
| ? || 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.
 +
| ? || Pagination || Support pagination (count, first, max) 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.  
 
|}
 
|}

Revision as of 09:09, 16 August 2012

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

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.  ? Pagination Support pagination (count, first, max) 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.