Simplify the creation of MetadataExtractor by not requiring
RSocketStrategies up front. The strategies are already configured in higher
level places like RSocketMessageHandler that invoke the MetadataExtractor.
The strategies are now passed in as an argument to the extract method.
@ -128,24 +123,26 @@ public class DefaultMetadataExtractor implements MetadataExtractor {
@@ -128,24 +123,26 @@ public class DefaultMetadataExtractor implements MetadataExtractor {
@ -166,8 +163,6 @@ public class DefaultMetadataExtractor implements MetadataExtractor {
@@ -166,8 +163,6 @@ public class DefaultMetadataExtractor implements MetadataExtractor {
@ -190,17 +185,17 @@ public class DefaultMetadataExtractor implements MetadataExtractor {
@@ -190,17 +185,17 @@ public class DefaultMetadataExtractor implements MetadataExtractor {
@ -208,7 +208,7 @@ public class RSocketMessageHandler extends MessageMappingMessageHandler {
@@ -208,7 +208,7 @@ public class RSocketMessageHandler extends MessageMappingMessageHandler {
@ -318,7 +318,7 @@ public class RSocketMessageHandler extends MessageMappingMessageHandler {
@@ -318,7 +318,7 @@ public class RSocketMessageHandler extends MessageMappingMessageHandler {
Assert.notNull(this.metadataExtractor,()->"No MetadataExtractor. Was afterPropertiesSet not called?");