>
> If this stuff is critical for your use, then I think it's fine to
> leave it in there, but IMO I don't think it is the correct place.
Thanks. But I will do the "right" thing. I don't think we should
allow hooks for each developer. I will remove them, but leave the
input validation classes in turbine.
The way I did it in the past, was to apply my patches to Column.java,
and the templates, generate my own peers and away I go. I can still
live under that model.
I do believe, however, that I can make a strong case for pushing
input validation all the way up to the peer level. Perhaps if we
get a chance to meet I can better desribe our enviorment and it's
needs.
mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
