Jonas Konrad

@dstepanov This PR addresses RoutingInBoundHandler, RequestLifecycle and so on. It is true that routing and execution logic is duplicated, but I do not see a way around this. The current...

I think a config option is unavoidable for 4.x. Though they are a bit reduced from 3.x with the MessageBodyHandler introduction, we *still* have many cases where certain decisions cannot...

yea i guess we can be more conservative with Object return type and skip a lot of the logic.

fyi @dstepanov when i'm on vacation, feel free to look at the routing side but please leave the netty pipeline alone, i have changes already lined up for that.

i added filter support, it added maybe 100ns static overhead + 100ns per filter. cors filter is still skipped to avoid those 100ns.

sure

@altro3 we've decided that for now the marginal perf benefit does not outweigh the maintenance effort of duplicating the routing code paths. this decision may change in the future however

Optional should be easy, it's just the code path above the ones that already changed. Will discuss in the meeting

also decided to test making this a ApplicationContextBuilder-level setting instead, will test.

@jameskleeh one problem with doing this as a more general setting is that we have to decide *now* where to implement this strict conversion checking. We can't add the stricter...