Peter Schneider-Manzell wrote: > > Hi! > I am responsible for the Acegi ACL tutorial, but unfortunately our own > server (which contained the source code example) crashed and we are still > trying to recover the files from our backups. >
That's sad to hear... :( You've done a great job documenting this but I'm too, as others here stuck atm... Something that puzzles me is that you define two DAO beans, basicAclObjectIdentityDAO and basicAclPermissionDAO, and autowire them into basicAclProviderManager. This implementation extends org.acegisecurity.acl.basic.BasicAclProvider wich requires basicAclDao to be set. Am I correct in assuming that basicAclPermissionDAO therefore should be renamed to basicAclDao? Secondly, the Acegi reference manual (page 87) mentions 4 methods of obtaining an object identity from a domain object: 1. Providing a getId() method on your domain objects, 2. implementing AclObjectIdentityAware on your domain objects, 3. alternative AclObjectIdentity implementation that accepts your domain object in its constructor or 4. overriding obtainIdentity(). I am uncertain of what approach you are following here, I have ruled out number 2 and number 4. You provide an alternative AclObjectIdentity implementation but it only acceps an object of type String in it's constructor, and I don't know if you wire this DefaultAclObjectIdentityClass in the AclProviderManager implementation? I believe it's not method 1 either, since I believe it would make BaseObjectACLAware superfluous. Could you please help clarify these two points? -- Thanks and regards, Stian B. -- View this message in context: http://www.nabble.com/Error-doing-ACL-example-tf2154101s2369.html#a8073234 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
