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"
< EclipseLink | Development | DBWS | RestfulComponent
Line 1: | Line 1: | ||
__NOTOC__== EclipseLink DBWS Restful Component Overview == | __NOTOC__== EclipseLink DBWS Restful Component Overview == | ||
<onlyinclude> | <onlyinclude> | ||
− | DBWS's Restful Component provides platform-neutral, JAX-RS compliant access to relational database artifacts via RESTful web services. EclipseLink's existing JPA and JAXB components are leveraged as well as the JAX-RS v1.1 reference implementation ([http://jersey.java.net Jersey]). | + | DBWS's Restful Component (DBWS-R) provides platform-neutral, JAX-RS compliant access to relational database artifacts via RESTful web services. EclipseLink's existing JPA and JAXB components are leveraged as well as the JAX-RS v1.1 reference implementation ([http://jersey.java.net Jersey]). |
− | DBWS at its core is primarily a design-time utility - an <i>application generator</i> - that with a minimum amount of pre-existing configuration plus a database to 'scrape' for meta-data, generates a simple CRUD-style application. | + | DBWS-R at its core is primarily a design-time utility - an <i>application generator</i> - that with a minimum amount of pre-existing configuration plus a database to 'scrape' for meta-data, generates a simple CRUD-style application. |
</onlyinclude> | </onlyinclude> |
Revision as of 09:12, 26 October 2011
EclipseLink DBWS Restful Component Overview
DBWS's Restful Component (DBWS-R) provides platform-neutral, JAX-RS compliant access to relational database artifacts via RESTful web services. EclipseLink's existing JPA and JAXB components are leveraged as well as the JAX-RS v1.1 reference implementation (Jersey).
DBWS-R at its core is primarily a design-time utility - an application generator - that with a minimum amount of pre-existing configuration plus a database to 'scrape' for meta-data, generates a simple CRUD-style application.