Changes between Version 2 and Version 3 of S2S_PERSISTENCE_COMMONS_R0
- Timestamp:
- 11/20/08 17:41:43 (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
S2S_PERSISTENCE_COMMONS_R0
v2 v3 8 8 9 9 == Overview == 10 There will be singleton class that will provide the connections and communications with the database. There will be entity classes that will correspond to tables in the database 10 There will be singleton class that will provide the connections and communications with the database. There will be Data Access Objects that 11 represent the persistence layer and communicate with the database. They will persist, update, delete and retrieve the objects used by the service and view layers. The scheme of the database will be created and used from the DAO(Data Access Object)s. 11 12 12 13 == Task requirements == 13 We must decide how we will implement the persistence of the entities to the database. We must design and implement the IDatabaseManager using some of the following approaches or something else : 14 * Use reflection and the entities property names? 15 * The entities are dictionaries with appropriate getters and setters? 16 * Static strings for names? 17 * Every entity has it's own persist, update, insert, etc methods, 18 that use IDatabaseManager? In that case the database manager will have 19 methods like openConnection and closeConnection... 14 Create the manager that communicates with the database. 15 Create the DAOs that will be needed from the other tasks in this revision. 16 Create the database schema to the extend needed by the other tasks in R0 20 17 21 18 We must decide if we will have opened connection all the time or for every action to the database we will open a connection. 22 19 23 20 == Task result == 24 The end result will be interface for communication with the database. 21 The end result will be interface for communication with the database. The DAO objects will use the connection to the DB 22 provided by the database manager and will be used directly only by the services. The DAO object will create queries to the database like: 23 {{{ 24 SELECT FROM USER password where username={?} 25 }}} 25 26 26 27 == Implementation idea == 27 ^(It is advisable to include some rough implementations ideas.)^ 28 The DAOs will be singleton that execute queries to the database using the DatabaseManager which is also singleton. The singleton 29 design pattern is used because of the many queries that will be executed at a time. 28 30 29 31 == Related == … … 31 33 32 34 == How to demo == 33 ^(In this section you must add instructions for the demo of the task.)^ 35 There will be JUnit tests for that task. The DAOs will be used by the service layer. 34 36 35 37 = Design =
