Mahendra Pratap wrote:Problem might be with your
try to debug this.
Mark Spritzler wrote:And ROLE_USER is how it is stored in your back end datasource for security, meaning your UserDetailService sets the GrantedAuthories as ROLE_USER. With ROLE_ as part of the role string, and all Caps?
Mark
Davie Lin wrote:What JSF implementation are you using?
I know for certain that JSF 1.1 does not have <f:ajax> tag
Nathan Pruett wrote:The base exception is here -
# 2010-05-04 18:32:48.138::WARN: Nested in org.springframework.beans.factory.BeanCreationException:
# Error creating bean with name 'org.springframework.security.config.http.UserDetailsServiceInjectionBeanPostProcessor#0':
# Initialization of bean failed; nested exception is java.lang.ClassCastException:
# org.springframework.transaction.annotation.AnnotationTransactionAttributeSource cannot be cast to
# org.openhds.dao.finder.FinderExecutor: java.lang.ClassCastException:
# org.springframework.transaction.annotation.AnnotationTransactionAttributeSource cannot be cast to
# org.openhds.dao.finder.FinderExecutor
# at org.openhds.dao.finder.Interceptor.invoke(Interceptor.java:19)
What's at org.openhds.dao.finder.Interceptor.invoke(Interceptor.java:19)?
What does the org.openhds.dao.finder.FinderExecutor class have in it?
David Newton wrote:Have them implement an interface.
I'm not saying not to do it with aspects, but you'd have the same problem with the class hierarchy unless you had as aspect for each type. At that point the complexity of an AOP solution outweighs just doing it normally.