第11讲架构与其他模式.pptVIP

对象标识符模式 * * Problem: Who should be responsible for materialization and dematerialization Info expert suggests the object should do this itself (i.e. direct mapping). But hard to program and to maintain. Solution: make a separate “database mapper” class responsible for materialization, dematerialization, object caching One for each persistent class * * 数据库映射器或代理模式 * * each mapper gets and puts objects in its own unique way, depending on the kind of data store and format 1 PersistenceFacade getInstance() : PersistenceFacade get( OID, Class ) : Object put( OID, Object ) ... ProductSpecification RDBMapper ... get( OID) : Object put( OID, Object ) ... ProductSpecification FlatFileMapper ... get( OID) : Object put( OID, Object ) ... Manufacturer RDBMapper ... get( OID) : Object put( OID, Object ) ... note that the Class as a parameter is no longer needed in this version of get , as the class is hardwired for a particular persistent type 1 ?interface? IMapper get(OID) : Object put( OID, Object ) ... Class UML notation : This is a qualified association. It means: 1. There is a 1-M association from PersistenceFacade to IMapper objects. 2. With a key of type Class, an IMapper is found (e.g., via a HashMap lookup) 模板方法模式 Problem: How to implement a variations of an algorithm that combine generic and specialized functionality? Solution: Provide a template method in base class that implements skeleton of algorithm, override varying parts in subclasses (using “hook” methods) * * * * Using template method pattern for materialization * * Abstract RDBMapper tableName : String + ?constructor? AbstractRDBMapper( tableName ) # getObjectFromStorage(OID) : Object {leaf} # getObjectFromRecord(OID, DBRecord) : Object {abstract} - getDBRecord(OID) : DBRecord Abstract PersistenceMapper + get( OID) : Object {leaf} # getObjectFromStorage(OID) : Object {abstract} ... { protected final Object getObjectFromStorage( OID oid ) { dbRec = getDBReco