Paulo Gaspar wrote:
> > > 2 - It is _major_ pain to implement a Map or a Collection, but
> > so easy to
> > > implement an Iterator;
> > > 3 - Some Iterators (like over some performant forward only ResultSets)
> > > naturally can not be reset. They are still damn useful.
> >
> > Right - I understand that the clueful of the world won't have a
> > problem. I am worried about those that don't realize the problems they
> > will run into. I am generally not a hand-holder, but we are trying to
> > make a simple, clean tool targeted towards simplicity for the designer,
> > a different skill set than the programmer. Yes, a programmer has to be
> > involved, but I am wondering how long it will be before someone puts
> > together a scriptable servlet where a designer can toss premade beans
> > into the context via external script/xml, etc, etc, etc...
>
> Well, from where I come they say:
> - Don't dress like a wolf if you aren't one.
Something must be lost in the translation :)
>
> > We can certainly support it. I would almost be rude not to. Maybe the
> > way to go is to holler and scream into the log when we run across a
> > naked Iterator....
>
> Yeah! On warning level!
done.
> > > Maybe I really need plugable introspection.
> >
> > You certainly need something...
>
> ...and I hope to get it here, since I don't get scared looking at Velocity
> source code. (But I sure do when looking at WM's.)
Why are WM's so scary?
geir
>
> And keep having fun,
> =:o)
>
> Paulo
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Velocity : it's not just a good idea. It should be the law.
http://jakarta.apache.org/velocity
