davsclaus commented on PR #26863: URL: https://github.com/apache/camel/pull/26863#issuecomment-5835900233
On the tie case in the overload matching: returning one of the tied candidates, rather than the fallback, is deliberate to leave out. On a tie there is no "right" choice. `Class.getConstructors()` and `getMethods()` don't guarantee any order, so picking the first tied candidate could make which constructor is used, and so how the bean is created, vary between JVMs. On a tie the previous behaviour applies: the fallback with an `Object` parameter, or none. So an ambiguous configuration fails the same way it did before, instead of silently picking one. As you say, the chance of hitting it is very low, so I'd leave it as is. _Claude Code on behalf of Claus Ibsen_ -- 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]
