Thanks a ton Nathan, I will definitely look into all the material you pointed me to.
Vanessa Pacheco Programmer Bowman Systems L.L.C 318.213.8780x307 ====================================== IMPORTANT WARNING: This message is intended for the use of the person or entity to which it is addressed and may contain information that is privileged and confidential, the disclosure of which is governed by applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this information is strictly prohibited. If you have received this message in error, please notify the sender immediately and arrange for the return or destruction of these documents. -----Original Message----- From: Nathan Anderson [mailto:[EMAIL PROTECTED] Sent: Thursday, March 20, 2008 12:51 PM To: [email protected] Subject: Re: [appfuse-user] Implementing Acegi ACLs Hi Vanessa, It looks like there are DAO's created in the tutorial. http://raibledesigns.com/wiki/Wiki.jsp?page=AppFuseAcegiACLAddDAO At the bottom of that step there are two Spring bean definitions that look like they were intended to be autowired like you expected. I'm guessing the tutorial was written for a different version of ACEGI than you are using and the API for ACL has changed. I know that ACEGI did have a major re-write of the ACL core, so that could be the problem. Unfortunately, I don't see anywhere in the tutorial where is says which version of ACEGI it was written for. In any case, the current ACL documentation should be up to date, so it may be a simple change (e.g. change the names of the DAO beans) to make it work. --- I just took a look at the following ACEGI documentation and it looks like the ACL API may have changed twice since the tutorial was written. http://www.acegisecurity.org/guide/springsecurity.html#domain-acls http://www.acegisecurity.org/guide/springsecurity.html#domain-acls-old The tutorial seems to match neither API exactly, but it is closer to the old model than the new model. Sorry, I can't help more, but hopefully that is enough information for you to dig in the right place for an answer ;) Nathan ----- [EMAIL PROTECTED] wrote: > Hi, I'm following the tutorial @ > http://raibledesigns.com/wiki/Wiki.jsp?page=AppFuseAcegiACL > > The bean definition for basicAclProviderManager is as below (copied > from tutorial) <bean id="basicAclProviderManager" > parent="txProxyTemplate"> <property name="target"> <bean > class="com.bmw.jcvs.service.acl.impl.BasicAclProviderManagerImpl" > autowire="byName" /> </property> </bean> Now since I use Appfuse 1.9.4 > (Spring 2.0), I defined it as follows <bean > id="basicAclProviderManager" > class="org.appfuse.service.acl.impl.BasicAclProviderManagerImpl" > autowire="byName > However, I get the error below. Now the tutorial > doesn't have a property referencing a Dao, so I thought that we didn't > need one. I thought autowire=byName would work in this case. Please > know that I'm a newbie and just learning all these tools and may not > really understand what's really needed. If someone could please > explain to me what's going on here and how to correct the issue, I'd > really appretiate it. > > org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'basicAclProviderManager' defined in > ServletContext resource [/WEB-INF/applicationContext-service.xml]: > Invocation of init method failed; nested exception is > java.lang.IllegalArgumentException: basicAclDao required > Caused by: > java.lang.IllegalArgumentException: basicAclDao required Thanks, > > > > Vanessa Pacheco > Programmer > Bowman Systems L.L.C > 318.213.8780x307 > > > > ====================================== > > IMPORTANT WARNING: This message is intended for the use of the person > or entity to which it is addressed and may contain information that is > privileged and confidential, the disclosure of which is governed by > applicable law. If the reader of this message is not the intended > recipient, or the employee or agent responsible to deliver it to the > intended recipient, you are hereby notified that any dissemination, > distribution or copying of this information is strictly prohibited. If > you have received this message in error, please notify the sender > immediately and arrange for the return or destruction of these > documents. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
