Source JAR in Maven doesn't include the Kotlin sources:

# unzip -l spark-kotlin-1.0.0-alpha-sources.jar
Archive:  spark-kotlin-1.0.0-alpha-sources.jar
  Length      Date    Time    Name
---------  ---------- -----   ----
       93  05-30-2017 23:37   META-INF/MANIFEST.MF
        0  05-30-2017 23:37   META-INF/
        0  05-30-2017 23:36   dummy/
        0  05-30-2017 23:37   META-INF/maven/
        0  05-30-2017 23:37   META-INF/maven/com.sparkjava/
        0  05-30-2017 23:37   META-INF/maven/com.sparkjava/spark-kotlin/
      920  05-30-2017 23:36   dummy/JavadocDummy.java
     8372  05-30-2017 23:36   META-INF/maven/com.sparkjava/spark-kotlin/pom.xml
      124  05-30-2017 23:37   META-INF/maven/com.sparkjava/spark-kotlin/pom.properties
---------                     -------
     9509                     9 files

Question/Feature request: I tend to write apps where the code is grouped by feature/package (opposed to group-by-layer) in order to achieve cleaner code, especially when it comes to larger codebases. I'm a newbie to Kotlin and haven't figured a way how to group routes into controllers using spark-kotlin, sparkjava supports this pattern. Is this possible, and if so how? In case it isn't, would it be possible to add support for it to spark-kotlin?

Hey,

This is a bit contradictory to https://github.com/perwendel/spark-kotlin/issues/7, however I was using a response transformer to generate JSON and noticed that the Kotlin wrapper didn't pass through the return values of the routes.

Cheers, Andreas

Hi! I try to run the basic example given on the project main page:

val http = ignite {
    port = 8080
    ipAddress = "0.0.0.0"
    threadPool {
        maxThreads = 10
        minThreads = 5
        idleTimeoutMillis = 1000
    }
}

http.get("/") {
    "Hello Spark Kotlin!"
}

but it gives already errors without doing a compile/build step, saying "Too many arguments for public fun ignite()". I would appreciate a working example or some hint, what goes wrong.

I added import spark.kotlin.* to the import section of my main.kt file and implementation "com.sparkjava:spark-kotlin:1.0.0-alpha" to my modules build.gradle dependencies section. And yes I triggered a gradle sync afterwards.

I'm trying out spark with Kotlin for the first time so forgive me if this is a trivial error but it seems to be in line with the documentation. I have created a folder in src/main/resources/public that contains an index.html

package com.divanvisagie.todo
import spark.kotlin.*


fun main(args: Array<String>) {

    val http: Http = ignite()

    staticFiles.location("/public")

    http.get("/hello") {
        "Hello Spark Kotlin!"
    }


    println("Hello Kotlin ?")
}

However browsing to the following url returns a 404.

http://localhost:4567/index.html

Hey ya, I like spark quite a bit and use it in multiple projects. I was wondering if framework can add banner functionality, just like Spring or Dropwizard?

Thank you.

In Java version I can app.exception(Exception::class.java) { e, req, res -> /**/ }

However, in this one the api seems to be unavailable, the IDE can't find any method with name exception. So how am I supposed to establish exception handling with instance API?

Hello happy people,

will there be a new(er) release any time soon? It seems that exception handlers (and maybe some other things I haven't touched yet) don't work in the latest release (from May, 2017) on maven central.

Are there anything to do before a release is possible that one can help with maybe?

Cheers, Alex

Since halt doesn't return, it should return Nothing. This can be accomplished by throwing the result of java's halt (it won't actually get thrown because java's halt will do it first).

This will let us use halt inside of when and the like without affecting the type of the expression. (right now, since halt returns the exception, a when statement will change its type to Any for no good reason)

request.queryParams can return null, which throws a runtime error since the return type of RouteHandler.queryParams is set as a non-nullable String: fun queryParams(key: String): String { return request.queryParams(key) }

There are probably other methods with the same problem (contentType?)

Right now, certain things are nullable from the Java side of things and are declared as non-null on the Kotlin side of things, which would cause runtime crashes as they occur. I think I covered them all here, but these were the ones that I found could be null via the JavaDocs of the Java libraries.

I also updated this to use the new java-library plugin which allows for more control over gradle dependencies.