But it helps to understand Injekt (light-weight dependency registry), Kovenant (promises library), and Klutter configuration injection to understand the complete sample. The docs for Kovert have links to code for starting Vertx and also starting a Verticle to use Vert.x-Web, so more sample code you can read. You can look at the code of Kovert to do your own similar work of starting and running Vert.x nicely, with Promises or however you wish. There is a full sample project of running Vert.x + Kovert

Vert.x nubes - not Kotlin specific, but makes Vert.x-Web friendlier for JVM languages. Kovert, a REST framework for Vert.x 3 - I am the author, one of my libraries Vert.x 3 helpers for Kotlin - by Cy6erGn0m Vert.x 3 module for Klutter - I am the author, one of my libraries You also then have debugging features of the IDE which are infinitely valuable.įor a few helper libraries for using Kotlin with Vert.x No need to set-up a Maven or Gradle build first to get going!Īnd really it is indeed just for prototyping and quick testing, and it isn't any faster than letting your IDE do the same and running from the compiled classes. This is really useful for quickly prototyping verticles and great for demos. Vert.x will compile the Java source file on the fly before running it. ployVerticle(SomeVerticleOfMine())Īlternatively, the docs for running and deploying from the command-line say: To do so, build your classes and run your own

You should try to use Vert.x 3 by running compiled code. ), and second that you need custom language support (

It doesn't really that was a Vert.x 2 thing they moved away from for compiled languages First that Vert.x 3 wants you to run Java/Kotlin files from source ( I think you are merging two thoughts into one. language_support.html' which is different than how it is now done in Vert.x 3. In the question, your link for language support says Vert.x 2 in the path 'vertx.io/

Compile kotlin online