ConstructorResolver error hints about mixing indexed and named args
This commit adds a note to an exception in `ConstructorResolver`'s `autowireConstructor` method hinting that attention should be paid to cases that mix indexed arguments and named arguments. This is especially when inheriting bean definitions in xml. Closes gh-29976 Close gh-PR
This commit is contained in:
committed by
Juergen Hoeller
parent
59c65fa940
commit
e262e98bab
@@ -294,7 +294,9 @@ class ConstructorResolver {
|
||||
}
|
||||
throw new BeanCreationException(mbd.getResourceDescription(), beanName,
|
||||
"Could not resolve matching constructor on bean class [" + mbd.getBeanClassName() + "] " +
|
||||
"(hint: specify index/type/name arguments for simple parameters to avoid type ambiguities)");
|
||||
"(hint: specify index/type/name arguments for simple parameters to avoid type ambiguities. " +
|
||||
"You should also check the consistency of arguments when mixing indexed and named arguments, " +
|
||||
"especially in case of bean definition inheritance)");
|
||||
}
|
||||
else if (ambiguousConstructors != null && !mbd.isLenientConstructorResolution()) {
|
||||
throw new BeanCreationException(mbd.getResourceDescription(), beanName,
|
||||
|
||||
Reference in New Issue
Block a user