wow that was dumb

I mean, I am dumb

maybe the example should do something like

@RequestMapping("/api")

to save someone else an hour of utter puzzlement 😄

@sdeleuze hi, do you think it’s a good idea to migrate to spring 5 right now or is it better to wait few months?

You mean for production ?

Yes

For a young start-up

So there is almost no users for now

I would wait RC1 I think

Before that we need to break a few APIs

Maybe M4 is doable if you like early stuff

We will release it shortly

By the way, a big step forward:

Kotlin reified type parameters are awesome

See https://github.com/mix-it/mixit/blob/master/src/main/kotlin/mixit/support/Extensions.kt#L34-L47 (will be replaced by native upcoming bean registering capabilities based on

Supplier

Sébastien, maybe this question is a bit broad but what are you thoughts on the big shift in Spring towards reactive web MVC? My feeling is that it is kind of an overkill for simple CRUD apps.. Maybe also don't fix what aint broken etc.. What do you think?

I expect no big shift, we will continue to support Spring MVC as today

We will provide the Spring Web Reactive engine in addition to regular Spring MVC

In an annotation or functional flavor

In the context of Kotlin, my gut feeling is that applications like the one I develop in https://github.com/mix-it/mixit/ is a good fit with Kotlin because it will allow more idiomatic code

No CGLIB proxies, more functional, etc.

But that’s not possible for every kind of app, for example if you use SQL today maybe better to stick with regular Sping Boot + Spring MVC stack

Also keep in mind the is Work in Progress

For example, the Web Functional API will be simplified tomorrow to remove some uneeded generics

Any feedback appreciated BTW

@sdeleuze funny i had been thinking about a kotlin dsl for bean registration 🙂

🙂

We may provide a it with Spring 5 so feel free to suggest ideas if you have

I mean we may provide Kotlin API out of the box