Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "EclipseLink/Development/DBWS/RestfulComponent/UseCases"

Line 28: Line 28:
  
 
There are three scenarios to consider:
 
There are three scenarios to consider:
# the database contains the Project's entities
+
# the database contains the Project's entities: the typical scenario where the Project's entities are exposed via a RESTful CRUD application.
# the database does <b>not</b> contain the Project's entities
+
# the database does <b>not</b> contain the Project's entities: the so-called <i>greenfield<i> scenario where the Project's entities do not yet exist on the database.
# meta-data describing the Project's entities is provided through an alternative mechanism
+
# meta-data describing the Project's entities is provided through an alternative mechanism: the scenario where the Project's entities are described via a JPA <tt>.orm</tt> file.

Revision as of 15:48, 17 October 2011

DBRS Use Cases

The DBRS utility starts by reading some initial configuration information:

prompt > DBRSBuilder [-builderFile {path to dbrsbuilder.properties}] -stageDir {path to stageDir}
         (if command-line arg -builderFile not present, default to look in current working directory)
prompt > DBRSBuilder running, connected to port 8884 ... Press <Return> to finish

dbrsbuilder.properties:

# builder properties
builder.port=8884
#builder.mode=production
builder.mode=test
builder.test.port=8885

# project properties
project.name=projectname
project.entities=employee, other entities ...

# database properties
db.driver=com.mysql.jdbc.Driver
db.url=jdbc:mysql://localhost:3306/db
db.user=user
db.pwd=password
db.platform=org.eclipse.persistence.platform.database.MySQLPlatform
logging.level=info

There are three scenarios to consider:

  1. the database contains the Project's entities: the typical scenario where the Project's entities are exposed via a RESTful CRUD application.
  2. the database does not contain the Project's entities: the so-called greenfield<i> scenario where the Project's entities do not yet exist on the database.
  3. meta-data describing the Project's entities is provided through an alternative mechanism: the scenario where the Project's entities are described via a JPA .orm file.

Back to the top