Yes, that would work. Thanks.
-tim
Hi Tim
Yes, the design does require the DAO provider know how to interpret the presented AclObjectIdentity.
As you know, JdbcDaoImpl (and any BasicAclDao for that matter) needs to be able to create BasicAclEntry[]s in response to the DAO request. Each BasicAclEntry has getAclObjectIdentity() and getAclObjectParentIdentity() methods, meaning the BasicAclDao needs to convert from row-data expressing this information into a new object instance. So, whilst your proposal caters for object -> database mapping, it doesn't address database -> object mapping.
I guess we could offer a pluggable interface within JdbcDaoImpl which does this conversion. ie:
public interface AclObjectIdentityStringResolver {
public AclObjectIdentity convertToIdentityObject(String identity);
public String convertToIdentityString(AclObjectIdentity aclObjectIdentity);
}
Would that address your needs?
Ben
------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Acegisecurity-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Acegisecurity-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
