日志记录中的切入点表达式问题，Spring AOP与log4j

Question

@Pointcut("execution(* com.mycomp..(..))")
private void businessService() {}  // signature

Caused by: java.lang.IllegalArgumentException: Pointcut is not well-formed: expecting
'name pattern cannot finish with ..' at character position 27
 execution(* com.mycomp..(..))

 @Pointcut("execution( com.xyz.someapp..service..(..))")

关于使用pointcut@around(value=“execution(*xyz.package.foo.bar..*(..))”）正如James所建议的那样，当我启动服务器时，我会遇到新的异常。

   Caused by: java.lang.IllegalStateException: Cannot convert value of type [$Proxy76 implementing org.springframework.context.ApplicationContextAware,org.springframework.aop.SpringProxy,org.springframework.aop.framework.Advised] to required type [com.mycompname.BancsContextAware] for property 'bancsContextAware': no matching editors or conversion strategy found
at org.springframework.beans.TypeConverterDelegate.convertIfNecessary(TypeConverterDelegate.java:264)
at org.springframework.beans.BeanWrapperImpl.convertIfNecessary(BeanWrapperImpl.java:448)
... 57 more

后来在调试中，我发现在其中一个类中我使用的是object.getClass().getAnnotation()，而由spring AOP创建的代理对象没有注释。正因为如此，我才得到了一个空指针异常。我使用aopproxyutils.ultimateTargetClass（someObject）对其进行了排序，但现在的问题是，我在com.mycom的子包中有一些最终的类和枚举。因为这个我得到了

nested exception is org.springframework.aop.framework.AopConfigException: 
Could not generate CGLIB subclass of class [class com.mycom.util.BancsServiceProvider]: Common causes of this problem include using a final class or a non-visible class; nested exception is java.lang.IllegalArgumentException: Cannot subclass final class class com.mycom.util.BancsServiceProvider
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:529)

那么如何从Spring AOP切入点中排除final类和枚举。

Answer 1

您正在寻找的切入点和方法如下所示：

@Around(value="execution(* xyz.package.foo.bar..*(..))")
public Object beforeAdvice(ProceedingJoinPoint jp) throws Throwable {
    //Get log4j logger for target class.
    Logger logger = LogManager.getLogger(jp.getTarget().getClass());

    logger.info(jp.getTarget().getClass().getName() + " " + jp.getSignature().getName() + " "
            + "Hit:");
    Object returnVal = jp.proceed(jp.getArgs());
    logger.info(jp.getTarget().getClass().getName() + " " + jp.getSignature().getName() + " "
            + "Finished:");
    return returnVal;
}

上面的代码将在进入方法之前记录类和方法名称以及“hit”，一旦以以下方式完成，则记录“finished”：

xyz.package.foo.bar.service.getPerson: Hit:
xyz.package.foo.bar.dao.getPerson: Hit:
xyz.package.foo.bar.dao.getPerson: Finished:
xyz.package.foo.bar.service.getPerson: Finished:
...

如果您想尝试遵循方法的多线程执行，只需使用以下方法：

@Around(value="execution(* xyz.package.foo.bar..*(..))")
public Object beforeAdvice(ProceedingJoinPoint jp) throws Throwable {
    Logger logger = LogManager.getLogger(jp.getTarget().getClass());

    String executionId = UUID.randomUUID().toString();

    logger.info(jp.getTarget().getClass().getName() + " " + jp.getSignature().getName() + " "
            + "Hit:" + executionId);
    Object returnVal = jp.proceed(jp.getArgs());
    logger.info(jp.getTarget().getClass().getName() + " " + jp.getSignature().getName() + " "
            + "Finished:" + executionId);
    return returnVal;
}