RockteMQ-AI commented on issue #701: URL: https://github.com/apache/rocketmq-spring/issues/701#issuecomment-5381846707
**Issue Evaluation** Category: | Status: **Evaluated** This is expected Spring behavior. When Spring scans for beans, it discovers both interfaces and their implementations. The annotation on your implementation class triggers Spring to register it as a transaction listener bean. The interface () itself is not instantiated as a bean unless explicitly annotated with or registered via . The implementation class () is the actual bean that gets created. If you are seeing the interface being treated as a bean, please check: 1. Whether the interface itself has a or similar stereotype annotation 2. Whether there is a method that explicitly creates an instance of the interface 3. Your component scan configuration — ensure it targets the correct package This is not a bug in rocketmq-spring; it is standard Spring IoC container behavior. --- *Automated evaluation by RockteMQ-AI* -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
