New updates have been posted to the repository, such as:
- additional Javadoc on existing interfaces and classes.
- added contract for Configuration.
- added a simple abstraction to handle uncaught exceptions.
- new elements such as Context, @Contextual and ObservableContext. These will help in gluing information between MVC members. I know we haven't really discussed how MVCs should look like but we're bound to have some kind of abstraction, regardless of if we call them MVC or not. I'd like to point you to an article posted last December on MVC, MVP, MVVM and PMVC in the context of the Griffon framework
The relevant bits are that even if this JSR advocates for what may be perceived as a single style (MVC) the API design may be able to handle additional patterns without so many changes, or none at all.
Before I can start a review I still think that we need to clarify some points:
Do we already defined the Java version on that the JSR should be based? I know that we had some discussions about that topic. Currently the grade.properties defines Java 8:
If we use Java 8 I would discuss some points of the API (example: using CompletableFuture in ThreadingHandler as a return value for all async methods)