|
|
(27 intermediate revisions by the same user not shown) |
Line 1: |
Line 1: |
− | __NOTOC__
| + | ignore |
− | ==EclipseLink DBRS Overview==
| + | |
− | <onlyinclude>
| + | |
− | The EclipseLink DBRS provides platform-neutral, JAX-RS compliant access to relational database artifacts via RESTful web services<sup>1</sup>. DBRS leverages EclipseLink's existing JPA and JAXB components as well as the JAX-RS RI Jersey (at the time of this writing, version 1.9).
| + | |
− | | + | |
− | EclipseLink DBRS is primarily a design-time utility.
| + | |
− | | + | |
− | </onlyinclude>
| + | |
− | | + | |
− | ====<sup>1</sup> RESTful web services (from Wikipedia) ====
| + | |
− | The term REST - <b>RE</b>presentational <b>S</b>tate <b>T</b>ransfer - was introduced and defined in 2000 by [http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm Roy Fielding in his doctoral dissertation] (Fielding is one of the principal authors of the HTTP v1.1 spec). Conforming to the REST constraints is referred to as being <b>RESTful</b>
| + | |
− | | + | |
− | A RESTful web service (also called a RESTful [http://en.wikipedia.org/wiki/Web_API web API]) is a simple web service implemented using HTTP and the principles of REST. It is a collection of resources, with four defined aspects:
| + | |
− | # use of URIs for all resources exposed by the web service: e.g. http://example.com/resources/car
| + | |
− | # use of Internet media types for on-the-wire representation. This is often JSON or XML, but can be any valid Internet media type.
| + | |
− | # use of the supported by HTTP v1.1 operations: POST, GET,PUT, and DELETE ([http://en.wikipedia.org/wiki/Create%2C_read%2C_update_and_delete typically mapped to the database semantics of CRUD: <b>C</b>reate, <b>R</b>ead, <b>U</b>pdate and <b>D</b>elete])
| + | |
− | # use of hyperlinks and URIs to interact with and navigate to resources.
| + | |