Notice: This Wiki is now read only and edits are no longer 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 6: | Line 6: | ||
# (<b>Meta-data Entities</b>) meta-data describing the specified entities is provided through an alternative mechanism: the scenario where the entities are described via a JPA <tt>.orm</tt> file. | # (<b>Meta-data Entities</b>) meta-data describing the specified entities is provided through an alternative mechanism: the scenario where the entities are described via a JPA <tt>.orm</tt> file. | ||
− | In its initial phase, DBWS | + | In its initial phase, DBWS-R 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 09:13, 26 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 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 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 entities are described via a JPA .orm file.
In its initial phase, DBWS-R 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)