Simon

This may be due to ``` fieldType = value.getClass(); // check that the serializer returned what it promised if (!fieldType.equals(typeSerializer.getSerializedType())) { Log.w(String.format("TypeSerializer returned wrong type: expected a %s but got...

Same problem here, but we have to deal with a 3rd-Party service where we cant change the return code. Any chances that the status handling will be changed?

That http status codes >= 300 are handled as an error.

@adriancole Everything good. :smiley: This topic should be handled very carefully. If the client returns a 302 since it cant open the url (http->https) or does not follow redirects it...

This could be useful if you are for example only interested in the headers returned by the resource.

This would also help to integrate aws messaging with spring cloud sleuth. Currently there is no non-invasive way to add tracing to sqs messages.

The same applies for reactive transaction management. Our testing shows that mixing spring and JOOQ leads to transactions not being rolled back: Config: ``` @Bean fun dslContext(connectionFactory: ConnectionFactory): DSLContext =...

@michael-simons Sure but my commet is about transactions and JOOQ in general and that the situation is also unclear in the reactive world.

Yep only using the preconfigured `io.r2dbc.spi.ConnectionFactory` and `ReactiveTransactionManager` from boot. The assumption was that it already provides everything needed. Thanks for the feedback though.

Thanks for the answer. I can see why terraform might be an option as it supports different cloud providers. On the hand it might make sense to use the platform...