A small Cycling web framework?

The court in the pros a question, someone interested in this topic. But I would like to no the pros and feedback. I do want to hear people's opinions, to debate.

Looks very cool. I understand you have implemented DI? It is very similar to Google Guice. At the same time in the juice does not have the normal web framework, but it's not something I would like. Don't want to do your library in the form of extensions to the juice?
\r
Another question: what is the use of type-safe template parameters? Once is validated for compliance with the properties in the interface and the placeholders in the template? If it is not present, the special sense in typing no, could be done just like in Spring MVC: the type of view.add("title", title), i.e. using string value of pacholder.
\r
And another question. How your frimware component? For example you can without much suffering to fasten as template engine XSLT?

A link to the trial version of add.

And there is no demo version. This same framework. What am I on this show? To put it in a sample application? Not significant. Because the application externally uninteresting, much more interesting is how it's written. That's why I gave the link to the tutorial. Here is an interesting application on top of the framework — make sure the demo version. But this is an entirely different project.

Wrote a review article on the library of the nop.sql, which is part of the framework. Who wants me to get it published — throw karma.

Looks very cool. I understand you have implemented DI? It is very similar to Google Guice. At the same time in the juice does not have the normal web framework, but it's not something I would like. Don't want to do your library in the form of extensions to the juice?

Yes, DI is realized, but I looked and figured that to do a simple DI is easier than to think about how to tie Guice. So did your simple DI
\r
\r

Another question: what is the use of type-safe template parameters? Once is validated for compliance with the properties in the interface and the placeholders in the template? If it is not present, the special sense in typing no, could be done just like in Spring MVC: the type of view.add("title", title), i.e. using string value of pacholder.

\r
Yes, the validation happens at compile templates. All templates are compiled at application start. The template language is statically typed. It's like one of the pieces of the template for which I began to do. By the way, the template itself is compiled into JVM bytecode, and inside it also takes into account the typing. There every template is compiled into a class, and parameters are physically represented as fields of the class.
\r
\r

And another question. How your frimware component? For example you can without much suffering to fasten as template engine XSLT?

Well, not entirely without particular pain. Need to implement your own Dispatcher'. However, in future versions I will provide an extension mechanism and DefaultDispatcher', which now renders templates to HTML. By the way, there are easier workarounds, but they smack of crutches. For example, methods of the controller can return an array of bytes. No one bothers to make the processing of an XSLT template and display it in a ByteArrayOutputStream. The second option is to write your own implementation of the Template. Still it is possible, conversely, to use the template engine without the framework.
\r
About XSLT. The template was conceived as some kind of replacement for XSLT. XSLT converts XML -> XML. I had the idea to make the conversion Bean -> XML, with a similar language. Well, with reduced features compared to XSLT, because the template specifies the presentation and not logic, and because it is impossible to give to the engine excessively cool possibilities, and then will have a you-know-what-language.

You have an interesting SQL DSL, but it seems that jooq in this case went further.