Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLink/Development/2.4.0/JPA-RS"
| Line 17: | Line 17: | ||
## Pass in all of the configuration | ## Pass in all of the configuration | ||
## Pass in minimal information with information about where to retrieve additional config from | ## Pass in minimal information with information about where to retrieve additional config from | ||
| + | |||
| + | == Using JPA-RS with static PU == | ||
| + | |||
| + | == Dynamic JPA-RS == | ||
| + | |||
| + | == Security == | ||
| + | |||
| + | There will be no security implemented with JPA-RS. Users wishing to secure their JPA-RS access should follow standard RESTful securing practices. | ||
| + | |||
| + | == Configurable Content == | ||
| + | |||
| + | By default all entity types CRUD operations and named queries will be exposed by JPA-RS. This must be made configurable so developers can specify what capabilities should be exposed. | ||
| + | |||
| + | === Additional URIs === | ||
| + | |||
| + | In addition to the URI's for all defined named queries and entity types there should be support in JPA-RS to access server side application logic within EJB session beans. | ||
Revision as of 15:22, 1 March 2012
Contents
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:
- 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
Using JPA-RS with static PU
Dynamic JPA-RS
Security
There will be no security implemented with JPA-RS. Users wishing to secure their JPA-RS access should follow standard RESTful securing practices.
Configurable Content
By default all entity types CRUD operations and named queries will be exposed by JPA-RS. This must be made configurable so developers can specify what capabilities should be exposed.
Additional URIs
In addition to the URI's for all defined named queries and entity types there should be support in JPA-RS to access server side application logic within EJB session beans.