you might recall that some time ago i posted about extending texen
aiming to generate source code from xml-schema
i've had this code working for quite a while now but i've been holding
off submitting until velocity 1.1 was released
(for those not familiar with texen)
(briefly) texen is an ant tasks that allows source code (amongst other
things) to be generated by velocity
the standard way that texen is used at the moment is by subclasses
extending texen to put different objects into the generation context
i'd like to propose a second (complementary) way to extend texen - by
creating nested elements within the task that put additional objects
into the generation context. this approach allows flexible 'tweaking' of
generation scripts (without having to write additional code) and also
enables better decoupling (of classes used in the generation from the
core velocity classes).
if you're interested, there are three ways that i can package the
classes (that extend texen in the proposed way)
1. by subclassing TexenTask (this means minimal disruption but also
means that other subclasses cannot use this functionality without being
rewritten)
2. by changing TexenTask itself
3. by creating an abstract superclass (available for other ant tasks
using velocity to inherit from - for example, anakia)
- robert
