Tag Archive: Java

Beanery – how to harden Snippetory’s type scheme

One of the things Snippetory doesn’t do better than most other engines is the string based coupling between the template and the Java code. Compared to untyped scripts it at least doesn’t break… Continue reading

Separation of concerns

Dealing with passive templates, I sometimes hear separating template and logic splits up things and makes it harder to maintain. I somewhat confused about that. I don’t solve my maintenance problems very often… Continue reading

JSP vs. Snippetory

I’m pretty aware, JSP is mature enough to get things done. However, working with passive templates I’ve learned, it can be done somewhat easier. At least for developers with not too much experience… Continue reading

  • The Snippetory project was started to demonstrate the power of passive templates with a strong abstraction layer. And as a way for me to reduce the need to work with JSP, which is a hassle once you got used to have the power and simplicity of passive templates at hand.

    More info on JProggy

  • Advertisements