On 6/23/01 7:42 AM, "robert burrell donkin" <[EMAIL PROTECTED]> wrote:
>
> so here goes...
>
> i started by looking at torque and thinking about producing a new
> subclass that places an object model parsed from a schema into the
> context. there are a number of reasons why - if possible - i didn't
> want to use this approach (in this case). one big reason was that i
> wanted to have the flexibility to be able to generate more sophisticated
> versions of the object model without having to change the subclass - or
> even change to using a general object model such as JDom or a DOM walker
> later.
>
> as far as i can see (maybe somebody would like to correct me), the
> fundamental way that all the velocity generation tasks work is by
> placing certain objects into context(s) and then running velocity. i'd
> agree that most of this stuff could certainly be achieved by extending
> how the properties file works instead - it's just that IMHO it's not as
> natural or powerful to achieve the effect in this way. nested elements
> allow the use of reflection to set properties on the beans before they
> are placed into the context. nested elements can also take advantage of
> ant's general infrastructure. of course, you could do most of this in
> the script - but another aim was to keep the scripts simple and readable.
Ok, even given the description above I'm still not really clear
on exactly what you're trying to do. Is your work on texen in the
ecs repository to look at or can you post a small example of
how your additions to texen might work?k
> - robert
--
jvz.
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
