Currently, there's no way to specify the mime type while using the BrokerRSocketRequesterBuilder bean created with the BrokerClientAutoConfiguration. Therefore, the dataMimeType for RSocket connector is resolved automatically from available decoders. First non-simple decoder on the list is used, which with the current boot RSocket config will end up resolving to application/cbor.
It would be helpful to allow the user to explicitly specify the data mime type used by the application for RSocket payloads.
Currently, there's no way to specify the mime type while using the
BrokerRSocketRequesterBuilderbean created with theBrokerClientAutoConfiguration. Therefore, thedataMimeTypefor RSocket connector is resolved automatically from available decoders. First non-simple decoder on the list is used, which with the current boot RSocket config will end up resolving toapplication/cbor.It would be helpful to allow the user to explicitly specify the data mime type used by the application for RSocket payloads.