How to organize complexity with JSP and Snippetory

To display data with template engines like JSP or all the others we often face the problem to organize pretty complex logic. Whenever we face a problem in programming outside of the templates… Continue reading

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

Feature announcement for Snippetory 0.9.5

Conditional Regions For a long time I have been thinking about conditional sections. I always thought to need a special syntax for this. This would have added complexity to the system and the… Continue reading

Maven Repository

Snippetory is now available in Maven Repository. This makes it easy to integrate it into projects. There’s a Maven Repository integration for almost any existing Java build tool. So, just add the dependency… Continue reading

Separation and abstraction

Once having the template freed from logic, new risks appear. Template code and technical issues of the output format might enter the logic site. This reduces the value of the separation, even it… 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

New tutorial

I added a new tutorial on  It shows the complete templating process using the Snippetory template engine. The example is based on reflection, to show the integration of tough logic.

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