Edgar Espina

Your 2nd second example should work. The way it works is like Parent/Child or MainRoute/SubRoute. So we can define all the routes/API/etc in children while main assemble everything and provide/setup...

yea, doc isn't never good enough. mount: https://jooby.io/#router-composing-mount > The mount operator only import routes. Services, callbacks, etc…​ are not imported. Main application is responsible for assembly all the resources...

found this too, but not sure how to fix it without introducing a break change. So probably this will be for 3.1 at least Have you look here https://jooby.io/modules/jte/? ```...

need to look into models, yea. But we need something to mark it requires a template engine and not a message encoder... they work more or less the same in...

Changes: - ` getModel()` - Remove all put method from ModelAndView - Replace `ModelAndView(String)` by `ModelAndView.map(String)` See #3395

should this be a Java annotation processor? Or something else?

How "binding" should work? Today: ``` { mvc(new Controller()); // DI version: mvc(Controller.class); } ``` Then we ask ServiceLoader to find the generated controller.

``` { mvc(new ControllerModule()); } ``` Why this isn't enough? I don't see the need of using ServiceLocator anymore.

@SentryMan which part? Said we have `Controller` and the new apt generates `ControllerModule.java` (we can call it any other way we want). So why keeping the ServiceLocator pattern (as we...

@SentryMan We can't do routes depends on order. @agentgt It is a good chance to get rid of ServiceLocator here. I think it is the best. Do any of you...