Spek works with Spring now? Would be good to include in this sample app.

^-- Sample application for Kotlin, Spring Boot, Spring Data Neo4j. Has features as would be typical of a social mobile application or web-app: - End users can interact (like, dislike) movies, roles or directors, make friends with other movie buffs, and based on these interactions, be recommended other movies to see. - Token-based authentication provided by Spring Security. It has a DTO mapping layer from reusable entities to use-case specific payload in/out. Pros of this is that its contract-first style. Cons is that it is an extra layer of boiler-plate. Could be replaced with GraphQL.

Maybe I'll add Spring Social to slurp Facebook data (liked movies) and act as an auth gateway (as would be typical of a mobile app)

class UserService @Autowired constructor(userRepo: UserRepository)
{
    private val userRepository: UserRepository = userRepo

why don’t just use?

class UserService(private val userRepository: UserRepository)

@enleur because it depends on the version of spring i think you can omit

@Autowired

from Spring 4.2 onwards

I have that version. I should remove it.

thank you

Hey guys, I'm getting a MappingException using

spring-data-mongodb

and Kotlin data classes. But it happens at random. I've tried adding

@PersistenceConstructor

and annotating each property with a

@Field

annotation, but it still happens.

`org.springframework.data.mapping.model.MappingException: No property null found on entity class

com.mycompany.Policy

to bind constructor parameter to!`

The class itself if just a data class

data class Policy(
  @Id var id: ObjectId? = null,
  val startDate: LocalDate,
  val endDate: LocalDate,
  val quote: Quote,
  var paymentTransaction: PaymentTransaction? = null
)

Just basic stuff

I've also tried with

data class Policy @PersistenceConstructor constructor( ... )

signature

Sometimes I would restart the app and spring-data-mongodb would refuse to load a previously saved record and throw up this error

@strelok Not a solution, but shot-in-the-dark guess at a possible work-around: Have you tried adding an empty default constructor?

I've been working with spring-data-neo4j and it does not have persistence constructors yet. Been in the backlog for a while.

@jasper thanks for the reply. Actually I debugged the cause and realised that at some point the parameters names from the constructor were lost (probably as part of kotlins incremental compilation) and not available to Java reflection(they would always be there for Kotlin Reflect). I had a chat to one of the devs in #general and the solution is to add the

-java-parameters

compiler flag which ensures the meta data is available to Java reflection.

I was meant to post it here but got side tracked

Aha - nice.

That makes sense

Why is

-java-parameters

not the default? I would prefer flawless interoperability over performance.

Ah because of incremental compilation.

Apparently it is equivalent to the javac

-parameters

flag. I'm not too sure. You know in Java nobody would write an entity with a constructor. It would just be a bunch fields annotated with whatever annotations you need

OK - makes sense.

You could create immutable entities, with dedicated constructors in Java. Uglier and not so common though.

Yes I think it's incremental compilation was messing it up. As if I cleaned and rebuilt it would work for a bit. Then randomly would stop as I stopped and restarted the app.

Yes exactly. That's what I mean nobody would do that in Java. Kotlin just makes it so easy :)

@iammiles has left the channel

Hi! is there an async http client that you would recommend for Kotlin ?

@rpalcolea https://docs.spring.io/spring/docs/5.0.0.RC1/javadoc-api/org/springframework/web/reactive/function/client/WebClient.html

With Kotlin extension provided in Spring JAR