@sss i have some additional code on top of vertx and vertx-async-sql

@sss lets go there, i'll show you

@hackerham thanks

I’m trying to create simple spring boot demo app with Kotlin and Spring cannot find my repository. App configuration

@SpringBootApplication
@EnableJpaRepositories
@ComponentScan("customer")
open class Application {
}

fun main(args: Array<String>) {
    SpringApplication.run(Application::class.java, *args)
}

Repository

interface CustomerRepository : JpaRepository<Customer, Long> {
}

Service

@Service
open class CustomerService(val repository: CustomerRepository) {
}

What am I missing here? 🙂

The error

Parameter 0 of constructor in customer.CustomerService required a bean of type 'customer.CustomerRepository' that could not be found.

@jakub.dyszkiewicz if I’m not mistaken, you have to annotate the repository. Also I think the service’s constructor needs to be annotated like this

open class CustomerService @Autowired constructor val repository : CustomerRepository)

@Autowried

annotation is not required when injecting via constructor since Spring 4.3

@Repository

is also not required when you extend

Repository

interface. Actually I moved Application class to package with repository and service and it started working so there is something definitely wrong with package scanning

but thanks anyway 🙂

Somehow I missed it 🙂 https://twitter.com/sparkjava/status/801900269076365312

Ahhhh that would be nice.

@fellshard what’s wrong with #ktor or #wasabi? They are both built on similar ideas of lean server definition.

Err. What's the context?

Wrong person?

@fellshard nope, context is sparkjava

Was mostly just thinking 'Spark in Kotlin could be nice.'

But I'm thinking Apache Spark, not SparkJava, so... never mind 😛

Ah, that’s something different 🙂

For those who want to see what next gen Kotlin + Spring project could look like: https://twitter.com/sdeleuze/status/808333678439002112

@sdeleuze IMO a test suite that contains a single integration test is not enough #opinionated

Sure, that’s just a start, we only have a 2 rest endpoints for now, it will quickly grow

@sdeleuze very cool. it would be nice to have one with a relational db. that's where things are interesting now (enough to have a whole channel #relational-sql dedicated to it).

Relational SQL + Reactive is not something easy, better to start with NoSql, but yes to would be nice. I may contribute Reactor for Requery and create a sample app.

@sdeleuze please do . A lot more of us probably use relational than nosql. In fact we use jsonb data structures in postgresql rather than mongodb . That is the trend i have generally seen work brilliantly

Yes but to have real end to end Reactive SQL support we need a non blocking JDBC only expected for Java 10

We may be able to work with Reactive API and dedicated thread pools with current JDBC drivers, but that’s not ideal

@sdeleuze we understand that . and accept that relational may not be 100% reactive. we will live with it. however we are already starting to make the move to kotlin/spring/vertx and are flabbergasted on how to use the relational part in a framework that may be reactive. i think your work will be a lifesaver there.

there is non-blocking driver for scala

that is used in vertx too

I use it in production 🙂