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/UseCases"
< EclipseLink | Development | DBWS | RestfulComponent
| Line 7: | Line 7: | ||
In its initial phase, DBRS will target the <b>Existing Entities</b> scenarios since that will satisfy the first two use cases (the <b>Greenfield Entities</b> scenario becomes a 'trivial' version of <b>Existing Entities</b>) | In its initial phase, DBRS will target the <b>Existing Entities</b> scenarios since that will satisfy the first two use cases (the <b>Greenfield Entities</b> scenario becomes a 'trivial' version of <b>Existing Entities</b>) | ||
| − | <onlyinclude> | + | </onlyinclude> |
Revision as of 17:01, 25 October 2011
DBWS Restful Use Cases
There are three scenarios to consider:
- (Existing Entities) the database contains the specified entities: the typical scenario where the Project's entities are exposed via a RESTful CRUD application.
- (Greenfield Entities) the database does not contain the specified entities: the so-called greenfield scenario where the Project's entities do not yet exist on the database.
- (Meta-data Entities) meta-data describing the specified entities is provided through an alternative mechanism: the scenario where the Project's entities are described via a JPA .orm file.
In its initial phase, DBRS will target the Existing Entities scenarios since that will satisfy the first two use cases (the Greenfield Entities scenario becomes a 'trivial' version of Existing Entities)