o.map | Open Street Map app - KaiOS | Map library

I have one big question here. While this is correct (it yields the same response) is this the correct thing to do?

Essentially, yes, you've done it correctly. The only things that aren't really correct there are your Webclient usage, and your style.

You certainly don't have to specify a WebClient per URI (and you shouldn't, they're meant to be reusable.) So if you have different domains and the same webclient, just create a standard instance:

'data' is a property of each dropped item.
So you can not append your existing info without extracting them from dropped items.

If you look at the documentation, in Observable Arrays, you could read this:

pop, push, shift, unshift, reverse, sort, splice

All of these functions are equivalent to running the native JavaScript array functions on the underlying array, and then notifying listeners about the change

When you do:

This works so you're probably not getting a ViewModel back from your webClient body but rather the map of parameters (or something) from the ViewModel.

Your CommentDTO has a property int CommentAuthor which is mapped from Employee.Name, which I assume is a string. It sounds like you need to make CommentAuthor a string.

Why do you need a state here? Can't you just do agreementInfos[index].agreement_scan_copy = res.data.data.url;?

componentDidMount only fires once per mount. If you want to run something every time the component re-renders, you need componentDidUpdate. Take a look at this lifecycle diagram for what method to use.

Be careful when using componentDidUpdate with this.setState. If you blindly update state every cycle in componentDidUpdate, you'll trigger an infinite loop. (See this answer for details.)

Yes, that's possible. But you need to modify the Id struct.

As far as I can understand you are using some generator to generate the source files. MyEntity for example. After generating the classes you need to manually modify Id struct. It should have an interface like this for example:

I would advice to re-think your vision about reactive stream and start avoiding calling that .block() manually.

Looking to your whole flow requirements, it is really better to make that fromR2dbcChannel as a FluxMessageChannel, so your Mono from R2DBC is going to be subscribed and processed smoothly internally by the framework if there is data.

Your @Transformer(inputChannel = "fromR2dbcChannel", outputChannel = "fromTransformer") then could just deal with a plain Event as an input parameter. Then your KinesisMessageHandler is good to deal with whatever you send to its input channel in the palyoad from that event.getDetails().

UPDATE

So, my bad. Independently of the channel for @InboundChannelAdapter, it still going to produce a Mono in the payload of the message. From here the channel type really doesn't matter. |But at the same time you can make that validationChannel as a FluxMessageChannel and then your transformer must be changed to the service activator: