Fix bug with the order of messaging arg resolvers
This commit is contained in:
parent
ebcee26d57
commit
750930fa25
|
@ -173,9 +173,6 @@ public class AnnotationMethodMessageHandler implements MessageHandler, Applicati
|
|||
|
||||
initHandlerMethods();
|
||||
|
||||
// Annotation-based argument resolution
|
||||
this.argumentResolvers.addResolver(new MessageBodyMethodArgumentResolver(this.messageConverter));
|
||||
|
||||
// Type-based argument resolution
|
||||
this.argumentResolvers.addResolver(new PrincipalMethodArgumentResolver());
|
||||
this.argumentResolvers.addResolver(new MessageMethodArgumentResolver());
|
||||
|
@ -183,6 +180,9 @@ public class AnnotationMethodMessageHandler implements MessageHandler, Applicati
|
|||
// custom arguments
|
||||
this.argumentResolvers.addResolvers(this.customArgumentResolvers);
|
||||
|
||||
// catch-all argument resolver
|
||||
this.argumentResolvers.addResolver(new MessageBodyMethodArgumentResolver(this.messageConverter));
|
||||
|
||||
// Annotation-based return value types
|
||||
this.returnValueHandlers.addHandler(new ReplyToMethodReturnValueHandler(this.dispatchMessagingTemplate));
|
||||
this.returnValueHandlers.addHandler(new SubscriptionMethodReturnValueHandler(this.webSocketSessionMessagingTemplate));
|
||||
|
|
Loading…
Reference in New Issue