For public use, these constants aren't ideally exposed through an SPI
like MetadataExtractor, and there isn't any other obvious place either.
In practice the only public API where these can be passed in is
RSocketRequester and RSocketMessageHandler both of which already
default to composite metadata anyway, leaving only the routing MimeType
to be used potentially but much less likely.
Due to existence of similar constants in the RSocket itself, i.e.
WellKnownMimeType, we can get by internally too without declaring
MimeType constants from a central place.
@ -153,7 +154,7 @@ public class DefaultMetadataExtractor implements MetadataExtractor {
@@ -153,7 +154,7 @@ public class DefaultMetadataExtractor implements MetadataExtractor {
@ -170,7 +171,7 @@ public class DefaultMetadataExtractor implements MetadataExtractor {
@@ -170,7 +171,7 @@ public class DefaultMetadataExtractor implements MetadataExtractor {
@ -59,7 +61,8 @@ final class DefaultRSocketRequesterBuilder implements RSocketRequester.Builder {
@@ -59,7 +61,8 @@ final class DefaultRSocketRequesterBuilder implements RSocketRequester.Builder {
@ -159,11 +162,14 @@ final class DefaultRSocketRequesterBuilder implements RSocketRequester.Builder {
@@ -159,11 +162,14 @@ final class DefaultRSocketRequesterBuilder implements RSocketRequester.Builder {
@ -171,14 +177,14 @@ final class DefaultRSocketRequesterBuilder implements RSocketRequester.Builder {
@@ -171,14 +177,14 @@ final class DefaultRSocketRequesterBuilder implements RSocketRequester.Builder {
@ -246,7 +252,7 @@ final class DefaultRSocketRequesterBuilder implements RSocketRequester.Builder {
@@ -246,7 +252,7 @@ final class DefaultRSocketRequesterBuilder implements RSocketRequester.Builder {
@ -73,7 +74,8 @@ public class RSocketMessageHandler extends MessageMappingMessageHandler {
@@ -73,7 +74,8 @@ public class RSocketMessageHandler extends MessageMappingMessageHandler {