Spider goes a step further requiring all attributes used in the template be listed using TypeTags; these tags serve both a documentation for the template as well as a type safe way to set attributes. See {@link StRenderable} for more docs.
Convention over configuration
=============================
Paradoxically having no choice can often be liberating; if there is only one way to do something the focus can simply be on actually getting it done.
Configuration for a web application tends to be very repetitive since most teams, if they are well organized, will adopt conventions to avoid having to check configuration files all the time. The configuration is thus copied and pasted each time a new module is added. In addition to being extra work this duplication also increases the maintenance burden.
Spider solves this by having no mandatory configuration (beyond the minimum required for a Java Servlet). A URI maps to a name of a class and the URI is valid if that class exists. Various parameters can be changed, however, but this is typically done by method overriding instead of external configuration files (which cannot be automatically refactored and are not checked at compile time).
|
|