tag:blogger.com,1999:blog-4353706559927087790.post2861833271139401461..comments2008-07-31T09:32:33.894+08:00Stephan Februaryhttp://www.blogger.com/profile/09641721620582976781noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-4353706559927087790.post-90151162809248149942008-07-31T09:32:00.000+08:002008-07-31T09:32:00.000+08:00Hi Stephan. Thanks for the post. This is exactly the info I was looking for. Do you know when your changes are likely to be included in a released version of the plugin? Also, I'm particularly interested in applying ACLs to method parameters. Any idea how long it'll be before that will be supported? I'd offer to help, but I'm just getting to know Spring Security and I haven't done any work on a Grails plugin.Matt Passellhttp://www.blogger.com/profile/11172160863136806601noreply@blogger.comtag:blogger.com,1999:blog-4353706559927087790.post-86683881917990298182008-07-07T10:51:00.000+08:002008-07-07T10:51:00.000+08:00@ramon: Please note that my changes are not in the official plugin yet, so you'll have to download the version linked to in the blog. <BR/><BR/>StephanStephan Februaryhttp://www.blogger.com/profile/09641721620582976781noreply@blogger.comtag:blogger.com,1999:blog-4353706559927087790.post-61514659716212339622008-07-07T10:49:00.000+08:002008-07-07T10:49:00.000+08:00kani: There is already experimental support for the annotations-based approach. Have a look at the Acegi plugin documentation at grails.codehaus.org<BR/><BR/>Personally I don't like the annotations-based approach, hence my "ACLBuilder" which I feel is more "Groovy" and also makes configuration easier. But this is my humble opinion. Nothing prevents us from providing both approaches.<BR/><BR/>StephanStephan Februaryhttp://www.blogger.com/profile/09641721620582976781noreply@blogger.comtag:blogger.com,1999:blog-4353706559927087790.post-87928145029723382962008-07-06T22:42:00.000+08:002008-07-06T22:42:00.000+08:00would you be adding annotation based ACL checks? I've never worked on Acegi/Springs security so I'm not sure if its already there. Wouldn't it be more easier to maintain.kanihttp://www.blogger.com/profile/13650619969611319765noreply@blogger.comtag:blogger.com,1999:blog-4353706559927087790.post-7359861132524502212008-06-13T18:41:00.000+08:002008-06-13T18:41:00.000+08:00Hi I get errors on my app and I am not able to run the script provided: grails create-acld-omains, neither CreateAclDomains. Grails says that both are not found. Can you please post the link to the newest one you have?Ramonhttp://www.blogger.com/profile/00400877164402263265noreply@blogger.comtag:blogger.com,1999:blog-4353706559927087790.post-76531962130000481172008-05-07T13:30:00.000+08:002008-05-07T13:30:00.000+08:00@Umut:<BR/><BR/>You will have to run the command:<BR/><BR/> >grails CreateAclDomains<BR/><BR/>Please refer to the example application download for more details.<BR/><BR/>Cheers<BR/>StephanStephan Februaryhttp://www.blogger.com/profile/09641721620582976781noreply@blogger.comtag:blogger.com,1999:blog-4353706559927087790.post-17077511705992195512008-04-26T19:53:00.000+08:002008-04-26T19:53:00.000+08:00Thank you for all your efforts and nice tutorial. <BR/><BR/>I guess I am missing something though, I am getting the following error: <BR/>[17031] errors.GrailsExceptionResolver groovy.lang.MissingPropertyException: No such property: AclObjectIdentity for class: LookupStrategyService<BR/>org.codehaus.groovy.runtime.InvokerInvocationException: groovy.lang.MissingPropertyException: No such property: AclObjectIdentity for class: LookupStrategyService<BR/><BR/>Is there something else I need to do like changing some additional configuration files, etc.? When I check the database created, I do not see any table other than the regular requestmap and roles acegi plugin creates. How does acegi store access control lists? <BR/><BR/>Kind Regards,<BR/>Umutumuthttp://www.blogger.com/profile/11876423563112200036noreply@blogger.com