Difference between revisions of "EclipseLink/Development/2.4.0/JPA-RS"
|Line 14:||Line 14:|
=== RESTFul API ===
=== RESTFul API ===
Revision as of 13:44, 6 March 2012
bug 362900 The EclipseLink 2.4.0 release will include an easy to use RESTful interface for interacting with JPA persistence units and EJB session bean methods. The intent is to provide an easy to use solution for exposing these Java EE capabilities through REST.
- Simple Enablement: The JPA-RS capability can be easily added to any Java EE application being deployed to any compliant Java EE server by simply adding JPA-RS components to an application.
- Zero configuration: When enabled the exposed JAX-RS service will allow any persistence unit or related EJB to be accessed using simple REST calls. Optional configuration will be supported for developers who want to limit what capabilities are exposed or wish to customize the resources used in any REST operation.
- Dynamic JPA-RS: Enable the deployment of a generic JPA-RS application into a compliant Java EE server without requiring any included persistence units. This dynamic service will support provisioning of persistence units on the fly by passing in or providing reference to dynamic JPA configuration XML (persistence.xml and eclipselink-orm.xml using virtual entities).
When enabled JPA-RS will expose the complete capabilities of the persistence units defined within the application.
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
The goal is to make enabling of JPA-RS as easy to do as possible.
In order to function in standard JAX-RS solution there must be annotated classes in the deployed WAR.
The JAX-RS reference implementation is Jersey (jersey.java.net). Additional support will be added to leverage Jersey's (add version) planned support for defining JAX-RS applications and resources using their API. The goal here is to allow JPA-RS to be declaratively configured without requiring any additional code to be included in a user's WAR/EAR.
Dynamic JPA-RS refers to the notion of a JPA-RS application deployment where persistence unit definitions are installed/provisioned on the fly.
There will be no security implemented with JPA-RS. Users wishing to secure their JPA-RS access should follow standard RESTful securing practices.
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.
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.