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"

(DBRS Use Cases)
(Replacing page with 'ignore')
 
(20 intermediate revisions by the same user not shown)
Line 1: Line 1:
== DBRS Use Cases ==
+
ignore
The DBRS utility starts by reading some initial configuration information:
+
<source lang="text" enclose="div">
+
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
+
</source>
+
 
+
There are three scenarios to consider:
+
# the database contains the specified entities: the typical scenario where the Project's entities are exposed via a RESTful CRUD application.
+
# the database does <b>not</b> contain the specified entities: the so-called <i>greenfield</i> scenario where the Project's entities do not yet exist on the database.
+
# meta-data describing the specified entities is provided through an alternative mechanism: the scenario where the Project's entities are described via a JPA <tt>.orm</tt> file.
+

Latest revision as of 15:37, 7 November 2011

ignore

Back to the top