RE: [FormProc-developer] RE: Validation by type

[Anthony E. <me...@an...>]

What gave you the idea that FormProc is a lightweight validation framework?
FormProc is in fact it is a form processing framework.  Part of form
processing, in my opinion, is to make it easier to store the form data in an
object, hence the auto population facilities provided by FormProc.  I
consider it part of the core functionality of FormProc.

Does anyone else have an opinion on this?  Do you like or dislike the way
FormProc auto populates objects?  Not that I am going to change it or
anything.  :-)

-Anthony

> -----Original Message-----
> From: Nick Bauman [mailto:ni...@co...]
> Sent: Wednesday, January 23, 2002 10:37 AM
> To: me...@an...
> Subject: RE: [FormProc-developer] RE: Validation by type
>
>
> Anthony,
>
> > widget and the FormElement class.  My reason for this is that the
> > FormElement does more than just validation - it also maps the form
> > field to a write method on a target object.  Thus having a single
>
> Howcome your framework has object population in addition to data
> validation? I mean isn't the population out of the context of a
> lightweight validation framework? It's like having a water pipe that does
> a loop-de-loop. It's pretty neat lookin', but it's having a
> strange effect
> on design, don't you think?
>
> I mean correct me: I'm not you and I'd be convinced if you could make a
> case for the coupling. Think of me as being too dumb to understand and I
> need to be enlightened. :)
>
> --
> Nick Bauman
> Java Programmer.
> Available Cheap.
> Minneapolis area.
> Will commute interstate.
> Resume: http://www.cortexity.com/resume.html
>