There's some work going on to make kotlin work better with spring but it's the 1.1 timeframe next year I think...

@orangy Any chance to have a feedback from somebody from the Kotlin team about the type inference issue I reported here https://kotlinlang.slack.com/archives/spring/p1479303727000195 ?

In order to identify if this could be improved on Kotlin 1.1

Did you submit a kotl.in/issue?

Nop because I am not sure that’s an issue yet but I can create an issue yes

Posting on Slack doesn’t guarantee anything, even if someone is in the channel and even if they read it. Human memory is so unreliable 🙂

OK I will create an issue

Issue created: https://youtrack.jetbrains.com/issue/KT-14923

@sdeleuze Thanks for reviewing, polishing, and committing my changes! 👍

You’re welcome

I plan to add more Kotlin feature

@Inject

and

@Autowired

support for sure in order to determine if a bean is require or not based ok Kotlin nullable information

Excellent, glad the ball is rolling now.

If anybody has good idea about what we should support in Spring in order to take advantage of Kotlin features

Feel free to propose here

We already support JSR 223 in Spring MVC Views

So when the 3 issues I have repported will be fixed, you will be able to use https://github.com/Kotlin/kotlinx.html based templates

But feel free to propose other ideas

@sdeleuze what are these 3 issues?

@orangy https://youtrack.jetbrains.com/issue/KT-14706 https://youtrack.jetbrains.com/issue/KT-14707 https://youtrack.jetbrains.com/issue/KT-14713

hey @sdeleuze i have some ideas that would be nice to hang in spring+kotlin but I can’t speak to the technical feasibility. I can bounce them off you if you like and submit the ones that make sense.

@yousuf.haque Yes feel free to propose here

Sweet! 1) When implementing a repository and a custom query method, it would be nice if we could leverage default methods on interfaces instead of having to do this:

public interface AccountRepository 
    extends JpaRepository<Account, Long>, AccountRepositoryCustom { ... }

public interface AccountRepositoryCustom {
    public void customMethod();
}

public class AccountRepositoryImpl implements AccountRepositoryCustom {

    @Autowired
    AccountRepository accountRepository;  /* Optional - if you need it */

    public void customMethod() { ... }
}

Our team adds extension methods onto the repository which seem to function equally well.

I am afraid limitations on default methods make that not possible, see http://stackoverflow.com/questions/26543612/should-i-use-java-8-default-methods-for-manually-implemented-spring-data-reposit for details

Extensions are more powerful so I guess that’s why you where able to achieve that. Could you share an example of extending Spring Data repository with Kotlin extensions ?

absolutely, one second

@User uploaded a file: Untitled

This is a very tiny example, but here’s a better one

using this kotlin jpa specifications library https://github.com/consoleau/kotlin-jpa-specification-dsl