Spring/spring-security
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Made BasicAclProvider to only respond to specified ACL object requests.

Browse Source
This commit is contained in:
Ben Alex
2004-11-09 21:09:14 +00:00
parent 11afb20856
commit f1d993f47b
3 changed files with 56 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
core/src/test/java/org/acegisecurity/acl/basic/BasicAclProviderTests.java
View File

@@ -184,6 +184,10 @@ public class BasicAclProviderTests extends TestCase {
provider.setBasicAclDao(new MockDao());
assertNotNull(provider.getBasicAclDao());
assertNull(provider.getRestrictSupportToClass());
provider.setRestrictSupportToClass(SomeDomain.class);
assertEquals(SomeDomain.class, provider.getRestrictSupportToClass());
}
public void testStartupFailsIfNullAclDao() throws Exception {
@@ -276,6 +280,16 @@ public class BasicAclProviderTests extends TestCase {
// this one SHOULD be supported, as it implements AclObjectIdentityAware
assertTrue(provider.supports(new MockDomain(4)));
// now restrict the provider to only respond to SomeDomain.class requests
provider.setRestrictSupportToClass(SomeDomain.class);
assertEquals(SomeDomain.class, provider.getRestrictSupportToClass());
// this one SHOULD be supported, as it has a getId() method AND it meets the restrictSupportToClass criteria
assertTrue(provider.supports(new SomeDomain()));
// this one should NOT be suported, as whilst it implement AclObjectIdentityAware (as proven earlier in the test), it does NOT meet the restrictSupportToClass criteria
assertFalse(provider.supports(new MockDomain(4)));
}
private JdbcDaoImpl makePopulatedJdbcDao() throws Exception {