3 ms·

Unfortunately it's not being properly maintained anymore. Last maven release was in Jul 10, 2022. It's maven dependencies have security issues and need to be up

Unfortunately it's not being properly maintained anymore. Last maven release was in Jul 10, 2022. It's maven dependencies have security issues and need to be updated to latest version. So if you want to use it you will need to do that.

topspin 3y ago
SparkJava has an actively developed fork/successor called Javalin[1]. It's straightforward to convert from SparkJava to Javalin. The latter is written in Kotlin but fully supports ordinary Java. While the rest of the Java world was devolving into annotation hell, AOP and other nightmares, these microframeworks showcased what happens when you leverage modern Java language features. A small but enthusiastic following has developed and they pop up now and then. [1] https://javalin.io/ https://javalin.io/
- weego 3y ago
  As a tiny data point, I've used javalin having moved from scala to kotlin and it's absolutely fantastic.
- AnyTimeTraveler 3y ago
  I've used Javalin as well and now I understand why it all looked pretty familiar, but I kept thinking "Javalin did x better". I can recommend Javalin as well! Having used the Spring Framework, this is a delight in comparison. Especially the setup is infinitely easier. (I know Spring Boot exists, but that's just a preselected pile of software that I have to understand)
  - usrusr 3y ago
    The spring boot dread: which of the defaults are a terrible idea to replace, and which of the defaults are a terrible idea to keep? I do wonder, when looking at the examples, if it might be nice to have a spark/javalin-like that depends on okhttp and reuses everything that appears on both sides of the connection. okhttpd if you like, even if perhaps still best built on top of jetty, like spark/javalin. Might have some skill reuse benefits, but might also cause some unintended shortcut accidents when the type system can't tell upstream from downstream objects.
    - rjst01 3y ago
      A big advantage that Javalin and some of the other micro-frameworks have over Spring Boot have is that by picking Spring boot, you are also implicitly picking Spring's custom Java classloader and packaging, and Maven or Gradle as a build tool. The tooling for building Spring Boot apps from other build systems like Bazel has problems, and while you can forego it and build your Spring Boot apps with Bazel's java_binary targets, you really don't want to. Javalin by contrast is a plain boring Java dependency and you can pull it into any Java app with ease. I do miss the better support for OpenAPI in Spring Boot though - Javalin's support is still missing a lot of functionality, but it is being very actively developed.

topspin 3y ago

SparkJava has an actively developed fork/successor called Javalin[1]. It's straightforward to convert from SparkJava to Javalin. The latter is written in Kotlin but fully supports ordinary Java. While the rest of the Java world was devolving into annotation hell, AOP and other nightmares, these microframeworks showcased what happens when you leverage modern Java language features. A small but enthusiastic following has developed and they pop up now and then. [1] https://javalin.io/ https://javalin.io/

weego 3y ago
As a tiny data point, I've used javalin having moved from scala to kotlin and it's absolutely fantastic.
AnyTimeTraveler 3y ago
I've used Javalin as well and now I understand why it all looked pretty familiar, but I kept thinking "Javalin did x better". I can recommend Javalin as well! Having used the Spring Framework, this is a delight in comparison. Especially the setup is infinitely easier. (I know Spring Boot exists, but that's just a preselected pile of software that I have to understand)
- usrusr 3y ago
  The spring boot dread: which of the defaults are a terrible idea to replace, and which of the defaults are a terrible idea to keep? I do wonder, when looking at the examples, if it might be nice to have a spark/javalin-like that depends on okhttp and reuses everything that appears on both sides of the connection. okhttpd if you like, even if perhaps still best built on top of jetty, like spark/javalin. Might have some skill reuse benefits, but might also cause some unintended shortcut accidents when the type system can't tell upstream from downstream objects.
  - rjst01 3y ago
    A big advantage that Javalin and some of the other micro-frameworks have over Spring Boot have is that by picking Spring boot, you are also implicitly picking Spring's custom Java classloader and packaging, and Maven or Gradle as a build tool. The tooling for building Spring Boot apps from other build systems like Bazel has problems, and while you can forego it and build your Spring Boot apps with Bazel's java_binary targets, you really don't want to. Javalin by contrast is a plain boring Java dependency and you can pull it into any Java app with ease. I do miss the better support for OpenAPI in Spring Boot though - Javalin's support is still missing a lot of functionality, but it is being very actively developed.