[FormProc-developer] Object Population and Validation (was: Validation by type)

[Nick B. <ni...@co...>]

I understand. That's great, I think it's a good idea. I was making an 
assumption that these are 2 different goals that s/b decoupled. It is, 
however, not wrong to couple them.

Thinking aloud: 

For myself, and maybe I need some religion on this one, but I personally 
don't like frameworks that make me change my objects to fit them better, 
or have to make discriptors of my objects that are external to them which 
make it possible for a framework to use them. For me to accept this, I'm 
going to take a long hard look before leaping. This is why I like the idea 
of decoupling the data validation from the object population. Maybe I want 
to plug in my own object population strategy? For this a peer interface is 
all that's needed. (If you've guessed that I dislike CORBA for this reason 
you're partially right, but only in particular when everyone is speaking 
Java, but that's another argument) 

Also, Anthony, the object population portion has taken root in your 
design. Is that a good thing? Maybe it is, but it makes me think. 

> 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