Shawn, Started working on the PropertyMgr interface we discussed, but wanted you to take a look before I flushed it out all the way
1. PropertyMgrImpl - https://github.com/PennState/directory-fortress-core-1/blob/feature/fc197ManageProperties/src/main/java/org/apache/directory/fortress/core/impl/PropertyMgrImpl.java - New property specific manager - Does checkAccess checks based on entity type (i.e. Role add/delete/update would require AdminMgrImpl.updateRole) 2. PropertyProvider Interface - https://github.com/PennState/directory-fortress-core-1/blob/feature/fc197ManageProperties/src/main/java/org/apache/directory/fortress/core/impl/PropertyProvider.java - Any DAO that supports properties must implement this (see https://github.com/PennState/directory-fortress-core-1/blob/feature/fc197ManageProperties/src/main/java/org/apache/directory/fortress/core/impl/RoleDAO.java) 3. PropertyP - https://github.com/PennState/directory-fortress-core-1/blob/feature/fc197ManageProperties/src/main/java/org/apache/directory/fortress/core/impl/PropertyP.java - Determines which DAO to use based on entity 4. New PropertyDAO - https://github.com/PennState/directory-fortress-core-1/blob/feature/fc197ManageProperties/src/main/java/org/apache/directory/fortress/core/impl/PropertyDAO.java - Can manage properties on objects that implement PropertyProvider ----- Original Message ----- From: "Shawn McKinney" <[email protected]> To: [email protected] Sent: Tuesday, October 18, 2016 1:47:17 PM Subject: Re: Fortress Properties > On Oct 18, 2016, at 12:35 PM, Shawn McKinney <[email protected]> wrote: > > exposes the physical data model to the caller which is never a good thing. Perhaps I was a bit hasty in saying this. To be clear, the physical data model is still hidden from the caller, although there is a new logical data mapping that has to be shared, i.e. attribute names inside the qb interface. Let’s experiment with the prop searches and if we see opportunities to use this pattern in the future, for new apis, we can do so.
