[Suggestion] Keep existing JHipster java config code and use kotlin only for entities about jhipster-kotlin HOT 3 CLOSED

Good point @PierreBesson

converting few thousand lines of code is really a big deal and it will change quite frequently. While interoperability between Java and kotlin is really good, there are some corner cases that had to be handled and I am more worried about that part.

Personally I would like 100% Kotlin project. But it seems to be wrong option to do at the moment (with many changes are pouring in from all the sides due to spring-boot-2).

It would be great to change the resource/service and domain + few config files into Kotlin and use them along with Java for the first release.

from jhipster-kotlin.

@deepu105 @PierreBesson in fact this is the same issue as we have for reactive code, see my comment here. I think we should have a common approach.

from jhipster-kotlin.

Hi, I did not dig deep yet into the reasons you want to keep Java for config, but if by "config" you mean java @Configuration annotated java classes probably as a "fast moving project" and, that said, being progressive and staying on the "edge" of available technologies maybe jhipster should consider ti use functional bean definitions for kotlin which seems more in line with jhipster-kotlin as well as cleans up the code. I always thought that config package in any spring project is quite a tie.
Here is the commit spring-projects/spring-framework@1f01146
and here is Spring Fu project https://github.com/spring-projects/spring-fu

Here are some startup bench-marking by Josh Long joshlong-attic/spring-fu@master...spring-projects:master#diff-52284b74457d055193be5c21586f2d98

from jhipster-kotlin.