You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Latest Framework snapshots are causing RSocketWebSocketNettyRouteProviderTests to fail with the following:
java.lang.IllegalArgumentException: No encoder for java.lang.String
at org.springframework.messaging.rsocket.RSocketStrategies.encoder(RSocketStrategies.java:61)
at org.springframework.messaging.rsocket.DefaultRSocketRequester$DefaultRequestSpec.encodeMetadata(DefaultRSocketRequester.java:274)
at org.springframework.messaging.rsocket.DefaultRSocketRequester$DefaultRequestSpec.lambda$getMetadata$6(DefaultRSocketRequester.java:252)
The request that can't be encoded has a MIME type of message/x.rsocket.routing.v0 that was added to Framework in this commit.
The text was updated successfully, but these errors were encountered:
wilkinsona
changed the title
Auto-configured RSocket strategies cannot encode message/x.rsocket.routing.v0 requests
Align with Framework changes to RSocket routing and new message/x.rsocket.routing.v0 requests
Jun 13, 2019
@bclozel@rstoyanchev Can you please confirm that this was the right change to make? Given that all mime types or just text/plain are the two options for CharSequenceEncoder it seemed reasonable. It's also the encoder that Framework's tests use so hopefully I'm not too far wide of the mark.
That's a reasonable change for now and in general, although you should be able to switch back to the stricter "text/plain" when spring-projects/spring-framework#23137 is resolved.
Latest Framework snapshots are causing
RSocketWebSocketNettyRouteProviderTests
to fail with the following:The request that can't be encoded has a MIME type of
message/x.rsocket.routing.v0
that was added to Framework in this commit.The text was updated successfully, but these errors were encountered: