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/DBWS/RestfulComponent/Overview"
| Line 11: | Line 11: | ||
</onlyinclude> | </onlyinclude> | ||
| − | ====<sup>1</sup> RESTful web services ==== | + | ====<sup>1</sup> RESTful web services (c.f. 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> | 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> | ||
Revision as of 14:45, 17 October 2011
EclipseLink DBRS Overview
The EclipseLink DBRS provides platform-neutral, JAX-RS compliant access to relational database artifacts via RESTful web services1. 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.
Configuration
A typical EclipseLink DBRS service - TBD
1 RESTful web services (c.f. Wikipedia)
The term REST - REpresentational State Transfer - was introduced and defined in 2000 by 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 RESTful
A RESTful web service (also called a RESTful 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 limited set of operations - GET, PUT, POST and DELETE - supported by HTTP v1.1
- use of hyperlinks and URIs to interact with and navigate to resources.