zeng-bohan commented on issue #12637: URL: https://github.com/apache/dubbo/issues/12637#issuecomment-5633181099
Thanks @PrakarshSrivastav — the issue is active. The fix is implemented in #16438: a `dubbo.application.reference-bean-naming-strategy` option that stops `@DubboReference` fields from colliding with `@Resource` by-name lookups. It ships with a test class, CI is green (30/30 checks, 100% patch coverage), and it has been waiting on a maintainer review since 2026-08-26. The most useful help right now would be **reviewing and testing that PR** rather than starting a parallel implementation: - Read the approach in #16438 and check it against the Spring injection model. @JerryOops's 2024-03 root-cause analysis above (field-name bean registration colliding with `@Resource`'s by-name lookup) is exactly the behaviour the naming strategy changes, so a second pair of eyes on the default (`field-name`, change is opt-in) would be genuinely valuable. - If you use Dubbo in your own project, pull the branch and try your scenario — a "worked for me" with your config is real evidence for the maintainers. On assignment: only Dubbo committers can assign issues, and since a complete implementation is already up, forking the work would slow this down — reviewing or testing #16438 (or extending it) is the contribution that gets it merged. @AlbumenJ could you take a look when you have a moment? Happy to adjust the approach based on your feedback. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
