|
From: Tim K. <tim...@gm...> - 2005-09-09 15:40:53
|
Following up on the previous email I sent yesterday, I explored one more=20 scenario. Since the hiearchy for the 'Service' interface is like this. Service=20 -'.get()' + TopicService (extends Service) - .getTopicList() - .getTopicChildren() And as I've mentioned in my previous email, the Acegi security method=20 interceptor does not seem to be kicking in on the 'get()' method when calle= d=20 on a TopicService implementation, although it does kick in for the other tw= o=20 methods defined under TopicService when using ProxyFactoryBean and=20 'interceptorNames' property.=20 So I tested out earlier today what would happen if I defined the 'get()'=20 method at the TopicService interface level, and updated the security method= =20 interceptor from com.vivakos.vps.service.Service.get=3DTOPIC_AFTER_ACL_READ to=20 com.vivakos.vps.service.content.Topic.get=3DTOPIC_AFTER_ACL_READ And the result is that it worked. So, I'm hoping that someone with a better= =20 understanding of what the differences between the ProxyFactoryBean advising= =20 process and the TransactionProxyFactoryBean would be - could clarify what i= s=20 going on, since to me, they should work the same? Thanks. -tim |