Spring AOP @Pointcut不会触发@Before方法

时间:2013-09-26 16:33:41

标签: java spring aop aspectj spring-aop

我有@Aspect和@Pointcut方法注释以激活@Before @Controller请求方法,它似乎匹配(因为我没有得到任何错误)但是它根本没有触发我的建议方法。为了测试目的,我将切入点更改为尽可能具体,并且在应用程序启动期间没有出现任何绑定错误。

这是我的控制器方法(该类是 com.x.y.z.MyController ):

@RequestMapping(method = RequestMethod.POST, produces = "application/json", consumes = "application/json")
@ResponseBody
public SubmissionResponse submitMethod(@Valid @RequestBody final SubmissionRequest request, HttpServletRequest httpRequest, BindingResult result)
{
    if (result.hasErrors()) { throw new BadRequestException(result); }

    //  ... do stuff ...
}

这是Aspect类:

@Aspect
@Component
public class RequestValidatingAspect
{
    private static final Logger LOGGER = Logger.getLogger(RequestValidatingAspect.class);

    @Inject
    private ClientService clientService;

    @Inject
    private AccountService accountService;

    @Pointcut("execution(* com.x.y.z.MyController.submitMethod(*.SubmissionRequest,*.HttpServletRequest,*.BindingResult)) && args(request, httpRequest, result)")
    private void requestValidation(SubmissionRequest request, HttpServletRequest httpRequest, BindingResult result) {} 

    @Before("requestValidation(request,httpRequest,result)")    
    public void theAdvice(SubmissionRequest request, HttpServletRequest httpRequest, BindingResult result) throws Throwable
    {
        System.out.println("Before - The Advice");
        LOGGER.info("Entering The Advice!");

        if(result.hasErrors()){ throw new BadRequestException(result); }
        // ... do stuff ...

        LOGGER.info("Exiting - The Advice!");
        return;
    }
}

2 个答案:

答案 0 :(得分:0)

事实证明@Pointcut线并不完全正确。 改变:

.. submitMethod(*.SubmissionRequest,*.HttpServletRequest,*.BindingResult) ..

submitMethod(..)或使用具有相同args过滤器的三个对象中的每个对象的完全限定类名允许建议锁定我想要的不同方法。我尽可能地改变了我的方法并创建了一个自定义注释来直接指示我想要哪些方法建议并完成最后一个切入点:

@Pointcut("@annotation(com.x.y.z.annotation.SpecificTypeOfRequestValidation) && args(request, httpRequest, result)")

答案 1 :(得分:0)

如果您使用的是Spring 4,那么您可以使用@ControllerAdvice注释来集中所有请求验证,从维护的角度来看这似乎更有帮助。