Revised NoSuchBeanDefinitionException message and ResolvableType handling
Includes consistent quoting of qualified type names in related classes. Issue: SPR-14831
This commit is contained in:
@@ -124,7 +124,7 @@ public class MessageMethodArgumentResolverTests {
|
||||
|
||||
assertTrue(this.resolver.supportsParameter(parameter));
|
||||
thrown.expect(MessageConversionException.class);
|
||||
thrown.expectMessage("the payload is empty");
|
||||
thrown.expectMessage("payload is empty");
|
||||
thrown.expectMessage(Integer.class.getName());
|
||||
thrown.expectMessage(String.class.getName());
|
||||
this.resolver.resolveArgument(parameter, message);
|
||||
@@ -216,7 +216,7 @@ public class MessageMethodArgumentResolverTests {
|
||||
|
||||
assertTrue(this.resolver.supportsParameter(parameter));
|
||||
thrown.expect(MessageConversionException.class);
|
||||
thrown.expectMessage("the payload is empty");
|
||||
thrown.expectMessage("payload is empty");
|
||||
thrown.expectMessage(Integer.class.getName());
|
||||
thrown.expectMessage(String.class.getName());
|
||||
this.resolver.resolveArgument(parameter, message);
|
||||
|
||||
Reference in New Issue
Block a user