zeng-bohan commented on PR #16438: URL: https://github.com/apache/dubbo/pull/16438#issuecomment-6116703396
Thanks for taking the time to look at this properly, @EarthChen — and for explaining the reasoning rather than just closing it. Your point lands: a local bean and a Dubbo proxy colliding on the same field name is a naming problem in the application, and adding a global `reference-bean-naming-strategy` switch would paper over it with configuration instead of fixing it. Offering `@DubboReference(id = "demo2Service")` as the explicit escape hatch keeps that decision where it belongs — in the application that has the collision. Closing this PR. I'll leave #12637 open so the underlying report stays visible, and the reproducer plus the test cases from this branch are on my fork if anyone hitting the same overlap wants a starting point. Thanks again for the review — good to have a clear answer on the design direction. -- 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]
