There is a general feeling that JXTemplateGenerator need to be refactored so it becomes more supportable, and also so that some components are possible in other parts of Cocoon, see:


A TemplateEngineDesign has been propsed and partially implemented:

Experimental stuff

Attribute Driven Templating

In some cases e.g. when using Dreamweaver, using attributes as template directives is better as it doen't disturb WYSIWYG. It might also make the templates less verbose and easier to read. This has been discussed in various threads and a design proposal can be found in AttributeTemplates:


There has also been discussions, design and implementation activities about factoring out the format part of templating and CForms to a separate layer:

XSLT/XQuery based templating

The idea of using XSLT or XQuery as template language was discussed in quite some detail in the beginning of 2003:

Although being an attractive templating solution in many ways, the conclusion back then was that it was to complicated to get efficient traversal of Java beans. Also there wasn't any good XQuery implementations that had a licence that was considered compatible with ASL either.

  • No labels