Jump to: navigation, search

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

Line 1: Line 1:
 
= EclipseLink JPA-RS =
 
= EclipseLink JPA-RS =
  
The EclipseLink 2.4.0 release is planning to include an easy to use RESTful interface for interacting with JPA persistence units. This page captures the requirements and design efforts. All feedback is welcome.
+
The EclipseLink 2.4.0 release is planning to include an easy to use RESTful interface for interacting with JPA persistence units. This page captures the requirements and design efforts. All feedback is welcome using the discussion page or through the {{bug|362900}}.
 +
 
 +
== Requirements ==
 +
 
 +
=== RESTFul API ===
  
 
[[EclipseLink/Development/2.4.0/JPA-RS/REST-API]]
 
[[EclipseLink/Development/2.4.0/JPA-RS/REST-API]]
 +
 +
=== Persistence Unit Access ===
 +
 +
In order for JPA-RS to access a persistence unit it must be made available through one of the following mechanisms:
 +
 +
# Available on classpath of running JPA-RS instance so standard JPA bootstrapping can find it
 +
# Provisioned: This requires a PUT call to the service to inform it of a PU
 +
## Pass in all of the configuration
 +
## Pass in minimal information with information about where to retrieve additional config from

Revision as of 10:27, 23 November 2011

EclipseLink JPA-RS

The EclipseLink 2.4.0 release is planning to include an easy to use RESTful interface for interacting with JPA persistence units. This page captures the requirements and design efforts. All feedback is welcome using the discussion page or through the bug 362900.

Requirements

RESTFul API

EclipseLink/Development/2.4.0/JPA-RS/REST-API

Persistence Unit Access

In order for JPA-RS to access a persistence unit it must be made available through one of the following mechanisms:

  1. Available on classpath of running JPA-RS instance so standard JPA bootstrapping can find it
  2. Provisioned: This requires a PUT call to the service to inform it of a PU
    1. Pass in all of the configuration
    2. Pass in minimal information with information about where to retrieve additional config from