> I mean, you would say that you had a unique problem, Velocity was 98% of
> the solution, and you were able to simple extend the package for your
> own purpose. That's a plus in favor of Velocity, if you ask me...
Sure is!
And the code is easy to understand to do just that.
Still, it would be even easier if I could plug the thing instead of
changing the code.
Hey, I am also being selfish here - I am also fed up of copy/pasting the
necessary code every time I upgrade Velocity!!!
=;o)
Have fun,
Paulo
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Geir Magnusson Jr.
>
> Paulo Gaspar wrote:
> >
> > Well, some of the things I do imply a modified version of Velocity that
> > accepts a different type of iterator.
> >
> > I use read-only forward-only Resultsets and I do not load them into
> > memory. I is possible to warp them in an "Iterator" but it is a solution
> > with some inconvenients.
> >
> > Let me think if I write the thing before or after proposing plugable
> > iterator types (I have a simple-to-implement idea for these).
>
> Or just tell us - one of the really valuable things about Velocity is
> that you can extend it as you wish for your own purposes, you don't have
> to ask permission, and you don't have to contribute back the changes.
>
> That is a very valuable statement in a use case, I think.
>
> I mean, you would say that you had a unique problem, Velocity was 98% of
> the solution, and you were able to simple extend the package for your
> own purpose. That's a plus in favor of Velocity, if you ask me...
>
> geir
>
> --
> Geir Magnusson Jr. [EMAIL PROTECTED]
> System and Software Consulting
> Developing for the web? See http://jakarta.apache.org/velocity/
> Well done is better than well said - New England Proverb
>
