Error type referred to is not an annotation type

I created a small project and played around AOP with Spring Native.

Sample Classes

Interface based service:

public interface HelloService {
    String hello();
}

public class HelloServiceImpl implements HelloService {
    public String hello() {
        return "Hello";
    }
}

Class based service:

public class HiService {
    public String hi() {
        return "Hi";
    }
}

Annotated class:

@Target({ElementType.TYPE, ElementType.METHOD})
@Retention(RetentionPolicy.RUNTIME)
@Documented
public @interface Greeter {
}

@Service
public class GreetingService {
    @Greeter
    public String greet() {
        return "Greeting";
    }
}

Aspect:

@Aspect
public class MyAspect {
    @Around(value = "execution(* com.example.demonativeaop.HelloService.*(..))")
    public String helloIntroduction(ProceedingJoinPoint joinPoint) throws Throwable {
        return joinPoint.proceed() + " (hello intercepted)";
    }
    @Around(value = "execution(* com.example.demonativeaop.HiService.*(..))")
    public String hiIntroduction(ProceedingJoinPoint joinPoint) throws Throwable {
        return joinPoint.proceed() + " (hi intercepted)";
    }
    @Around(value = "@annotation(com.example.demonativeaop.Greeter)")
    //    @Around(value = " within(com.example.demonativeaop..*) && @target(com.example.demonativeaop.Greeter)")
    public String greeterIntroduction(ProceedingJoinPoint joinPoint) throws Throwable {
        return joinPoint.proceed() + " (greeter intercepted)";
    }
}

Here are some of the findings and improvement ideas.

@Aspect class

MyAspect class is annotated with @Aspect.

Declared as @Bean

When MyAspect is declared as a @Bean:

    @Bean
    public MyAspect myAspect() {
        return new MyAspect();
    }

The reflect-config.json requires this entry.

  {
    "name": "com.example.demonativeaop.MyAspect",
    "allDeclaredMethods": true
  }

This is because methods in the @Aspect class define pointcuts, but usually they are not referenced by the application.
Those methods need to be retained to create AOP proxies.

Improvement idea

Automatically add hint when a bean with @Aspect is found.

Annotated as @Component

When MyAspect class is annotated with @Componenet, the component scan finds the bean.
In this case, no manual configuration is required.

@Aspect
@Component
public class MyAspect {
    ...
}

The generated reflect-config.json has this entry:

  {
    "name": "com.example.demonativeaop.MyAspect",
    "allDeclaredFields": true,
    "allDeclaredConstructors": true,
    "allDeclaredMethods": true,
    "allPublicMethods": true,
    "allDeclaredClasses": true,
    "methods": [
      {
        "name": "<init>",
        "parameterTypes": []
      }
    ]
  }

Reference in AOP expression

For a pointcut expression execution(* com.example.demonativeaop.HiService.*(..)), the reflect-config.json requires this entry:

  {
    "name": "com.example.demonativeaop.HiService",
    "allDeclaredMethods": true
  }

Otherwise, this exception is thrown at runtime:

...
Caused by: java.lang.IllegalArgumentException: warning no match for this type name: com.example.demonativeaop.HiService [Xlint:invalidAbsoluteTypeName]
	at org.aspectj.weaver.tools.PointcutParser.parsePointcutExpression(PointcutParser.java:319) ~[na:na]
	at org.springframework.aop.aspectj.AspectJExpressionPointcut.buildPointcutExpression(AspectJExpressionPointcut.java:227) ~[na:na]
...

For annotation based pointcut, @annotation(com.example.demonativeaop.Greeter), it requires the annotation to be in reflect-config.json as well.

  {
    "name": "com.example.demonativeaop.Greeter",
    "allDeclaredMethods": true
  }

Without the entry, this error is thrown:

...
Caused by: java.lang.IllegalArgumentException: error Type referred to is not an annotation type: com$example$demonativeaop$Greeter
	at org.aspectj.weaver.tools.PointcutParser.parsePointcutExpression(PointcutParser.java:319) ~[na:na]
	at org.springframework.aop.aspectj.AspectJExpressionPointcut.buildPointcutExpression(AspectJExpressionPointcut.java:227) ~[na:na]
...

Improvement idea

It would be nice if AOT parses the AOP expression and figures out any classes that has reference to, then auto generate hints for them.

AOP Proxies

In spring-native, there are two phases for AOP proxies.

The first phase is at AOT.
For class based proxies, ConfigurationContributor and ProxyGenerator generate proxy classes with ByteBuddy(e.g. com.example.demonativeaop.HiService$$SpringProxy$7f5de2cd) and write class files under target/generated-sources/spring-aot/src/main/resources/../*.class.
Also, it adds the generated proxies to the reflect-config.json in order for runtime to read them.

The next phase is at runtime.
The Target_DefaultAopProxyFactory substitutes the AOP proxy creation.
For class based proxies, it uses BuildTimeAopProxy(ObjenesisBuildTimeAopProxy) which loads the ByteBuddy generated proxies and instantiate them.

To bridge these two phases, the ProxyConfiguration#getProxyClassName() method guarantees the same name is generated based on the advised interfaces.

Class based proxy:

The HiService is a class based proxy service.
In order to generate a proxy for this class at build time, this hint is required.

@AotProxyHint(targetClass=com.example.demonativeaop.HiService.class, proxyFeatures = ProxyBits.IS_STATIC)

The hint is read by ConfigurationContributor#generateBuildTimeClassProxies and generates ByteBuddy proxy classes.(e.g. com.example.demonativeaop.HiService$$SpringProxy$7f5de2cd)

Improvement Idea

Currently, the user needs to add @AotProxyHint to trigger the ByteBuddy proxy generation.
It would be nice if this is not required; so that, build time automatically detects class based proxies for AOP and generates/persists proxies.

Interface based proxy

The HelloService is interfaced based proxy service. (with HelloServiceImpl)

This uses JdkDynamicAopProxy to generate AOP proxy at runtime.

Since this is a regular dynamic proxy at runtime, proxy-config.json requires this entry.

  [
    "com.example.demonativeaop.HelloService",
    "org.springframework.aop.SpringProxy",
    "org.springframework.aop.framework.Advised",
    "org.springframework.core.DecoratingProxy"
  ]

Improvement idea

Since this proxy entry is infrastructure logic to generate dynamic proxy, it would be nice that AOT automatically adds this hint at build time.

Я новичок в АОП и AspectJ. Я пытаюсь написать собственную логику для пользовательской аннотации с типом элемента TYPE. Я также хочу использовать параметры в моей аннотации, чтобы написать собственную логику внутри метода around. Я получаю указанную ниже ошибку. Я пробовал читать несколько источников, и большинство из них связано с использованием @annotation. Мне трудно понять то же самое. Может кто-нибудь объяснить, почему следующий способ с @within не работал с каким-то ясным примером?

Аннотация (Slf4jTrace.java):

package io.ud.project.falcon.logging;

import io.ud.project.falcon.logging.generator.AbstractLogTraceIdGenerator;
import io.ud.project.falcon.logging.generator.DefaultLogTraceIdGenerator;

import java.lang.annotation.ElementType;
import java.lang.annotation.Retention;
import java.lang.annotation.RetentionPolicy;
import java.lang.annotation.Target;

@Target(ElementType.TYPE)
@Retention(RetentionPolicy.RUNTIME)
public @interface Slf4jTrace {

    String traceKey() default "traceId";

    Class<? extends AbstractLogTraceIdGenerator> traceValueGenerator() default DefaultLogTraceIdGenerator.class;

}

Компонент аспекта (Slf4jTraceAspect.java):

package io.ud.project.falcon.logging;

import lombok.extern.slf4j.Slf4j;
import org.aspectj.lang.ProceedingJoinPoint;
import org.aspectj.lang.annotation.Around;
import org.aspectj.lang.annotation.Aspect;
import org.aspectj.lang.annotation.Pointcut;
import org.springframework.stereotype.Component;

@Aspect
@Component
@SuppressWarnings("unused")
@Slf4j
public class Slf4jTraceAspect {

    @Pointcut("execution(public * *(..))")
    public void publicOperation() {
        //Using this pointcut annotation for Around method.
    }

    @Around(value = "@within(slf4jTrace) && publicOperation()")
    public void logTrace(ProceedingJoinPoint joinPoint, Slf4jTrace slf4jTrace) throws Throwable {
        //Custom logic that uses slf4jTrace's parameters        
        joinPoint.proceed();
        //Custom logic that uses slf4jTrace's parameters
    }
}

Аннотированный класс (Foo.java):

package io.ud.project.falcon.logging;

import io.ud.project.falcon.logging.Slf4jTrace;

@Slf4jTrace(traceKey = "auditID")
public class Foo {

    public void doSomething() {
        //Something happens here.
    }

}

Ошибка при запуске приложения:

, 2021-01-02 22:16:41,340, ERROR [main] o.s.b.SpringApplication.reportFailure(833) | Application run failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'objectMapperConfigurer' defined in springfox.documentation.spring.web.SpringfoxWebMvcConfiguration
: BeanPostProcessor before instantiation of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration': BeanPostProcessor before instantiation of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.cache.annotation.ProxyCachingConfiguration': Initialization of bean failed; nested exception is java.lang.IllegalArgumentException: error Type referred to is not an annotation type: slf4jTrace
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:497)
        at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:312)
        at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:228)
        at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:310)
        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:205)
        at org.springframework.context.support.PostProcessorRegistrationDelegate.registerBeanPostProcessors(PostProcessorRegistrationDelegate.java:238)
        at org.springframework.context.support.AbstractApplicationContext.registerBeanPostProcessors(AbstractApplicationContext.java:709)
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:534)
        at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:140)
        at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:752)
        at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:388)
        at org.springframework.boot.SpringApplication.run(SpringApplication.java:327)
        at org.springframework.boot.SpringApplication.run(SpringApplication.java:1246)
        at org.springframework.boot.SpringApplication.run(SpringApplication.java:1234)
        at io.ud.project.falcon.FalconApplication.main(FalconServiceApplication.java:65)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48)
        at org.springframework.boot.loader.Launcher.launch(Launcher.java:87)
        at org.springframework.boot.loader.Launcher.launch(Launcher.java:50)
        at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:51)