Use Java annotation processor instead of GWT Generator?

[metteo]

GWT Generators are going away in GWT 3 / j2cl. They only way forward is apt. The added benefit of migration would be out of the box support for non GWT projects like Java and Android ones.

However there are sharp alternatives supporting JSR-330:

• google/dagger as a base
• google/auto/factory for assisted inject

but some Gin / GWT specific features are not supported by them:

• GWT-RPC Sync / Async interfaces
• AsyncProvider interface

More on the issue here: GWT 3 and Gin

Consider either migration to apt or creation of dagger extensions to support GWT specific features.

[metteo]

One option would be an annotation processor which reads Gin DSL and generates Dagger modules and component. The Ginjector could then delegate to Dagger @Component class. GWT extensions could be hidden this way. Unfortunately it would mean that Guice specific syntax would stop working.

[ibaca]

FYI

This autorpc-gwt project creates Sync/Async GWT-RPC interfaces, optionally with an RxJava async interface too.

And reactivity which is a dagger + code-splitting sample project. I bit more manual work required, but almost no dependency (no library code) except dagger. I use RxJava but native JS promises (or just a callback) can be used instead to add zero codesize overhead.