Principled Java code generation

Overview

The core underlying concept of guardrail seems doable in Java; one challenge would be maintaining the flexibility of the various typeclasses without global registries. Explicit value passing and typechecking responses.

Details

The biggest advantage I see for providing this would be to permit an easier migration path from existing Java services into Scala, by first following best practices isolating the business logic from the web framework and using generated models+encoders/decoders for all communication, then migrating the business logic piecemeal into Scala by using scala-java8-compat to adapt down to toCompletableFuture.

Progress

• Encode existing Free algebras with knowledge of which language they are targeting
• Remove all references to scala.meta from everything but the ScalaLanguage specification class and the generators
• Add a language parameter to the argument parser/context
• Add a java generators for akka-http clients and servers, using javaparser
• Add a Jackson generator, wire it in to the java-akka stuff according to the docs

[kelnos]

Just as an update here, we have full Java support in the core now, and generators for Dropwizard servers and AsyncHttpClient clients. At this point, adding Java akka-http servers and clients is just a matter of deciding on the generated output and writing generators.

[kelnos]

Heh, I guess this can be closed.