yx-Yaoxaing opened a new pull request, #596:
URL: https://github.com/apache/rocketmq-spring/pull/596

   ## What is the purpose of the change
   Originally, when annotating a class with @Configuration, it couldn't be 
resolved as a RocketMQ consumer listener class. I changed the way annotations 
are parsed, allowing classes marked with @Configuration to be correctly 
identified as RocketMQ consumer listener classes. This is because, in our 
practice at the company, many people also prefer using @Configuration.
   ## Brief changelog
   In the postProcessAfterInitialization() method of the 
RocketMQMessageListenerBeanPostProcessor message listener post-processor, I 
changed the annotation processing approach to:
   RocketMQMessageListener ann = (RocketMQMessageListener) 
AnnotationUtils.findAnnotation(targetClass, RocketMQMessageListener.class);
   This modification allows both @Configuration and @Service annotated classes 
to function as consumer listeners.
   ## Verifying this change
   In production and actively deployed.
   RocketMQMessageListener ann = AnnotationUtils.findAnnotation(targetClass, 
RocketMQMessageListener.class);
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to