Wishes,
Peter
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Jason Daiger
Sent: Tuesday, June 13, 2006 5:19 PM
To: CFCDev@cfczone.org
Subject: RE: [CFCDev] Model or View?
Only if all of your validation is against single objects or manageably
small collections
@cfczone.org
Subject: Re: [CFCDev] Model or View?
I would caution against pulling validation out of the domain model entirely,
since it could lead to Fowler's Anemic Domain Model
antipattern:
http://www.martinfowler.com/bliki/AnemicDomainModel.html
It's also worth emphasizing that putting
!
Best Wishes,
Peter
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf
Of Jason Daiger
Sent: Tuesday, June 13, 2006 5:19 PM
To: CFCDev@cfczone.org
Subject: RE: [CFCDev] Model or View?
Only if all of your validation is against single objects or
manageably
PROTECTED] On Behalf
Of Chris Scott
Sent: Wednesday, June 14, 2006 8:12 PM
To: CFCDev@cfczone.org
Subject: Re: [CFCDev] Model or View?
I think that the discussions that Martin Fowler has raised in his
post about the 'AnemicDomainModel' are definitely quite interesting,
and by all means worth
] [mailto:[EMAIL PROTECTED] On Behalf
Of Cliff Meyers
Sent: Wednesday, June 14, 2006 4:40 PM
To: CFCDev@cfczone.org
Subject: Re: [CFCDev] Model or View?
I would caution against pulling validation out of the domain model entirely,
since it could lead to Fowler's Anemic Domain Model
antipattern:
http
Lots of good discussion here.
The big question is where your business logic goes. ADM is an
approach where the data contructs (beans/domain model) are operated
upon by methods in your service layer. Here the domain objects are
often called dumb data holders that don't really have any behavior
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf
Of Cliff Meyers
Sent: Wednesday, June 14, 2006 4:40 PM
To: CFCDev@cfczone.org
Subject: Re: [CFCDev] Model or View?
I would caution against pulling validation out of the domain model entirely,
since it could lead
That's why you have to budget at least a little time for the
all-important refactoring: because we all screw it up the first time
around... or sometimes more than that! :)
On 6/14/06, Nando [EMAIL PROTECTED] wrote:
I'm currently thinking through a model and the more i do this, the more i
What i do, cuz i'm a little intellectually lazy, like Ray, is to place
a validate
function in my bean. Others abstract the validation to a separate
object, but i
prefer having it in one package. It's just a little easier for me to
see what's
going on.
I think there are two different kinds of
@cfczone.org
Subject: RE: [CFCDev] Model or View?
What i do, cuz i'm a little intellectually lazy, like Ray, is to place
a validate
function in my bean. Others abstract the validation to a separate
object, but i
prefer having it in one package. It's just a little easier for me to
see what's
going on.
I
To: CFCDev@cfczone.org
Subject: RE: [CFCDev] Model or View?
Nice to see a posting that isn't spam!!!
RADEMAKERS Tanguy said:
- On the one hand, you have a type of format checking that's essentially
about type safety, and that operates on single fields. If you have an object
that exposes an email
.
Best of luck with the refactoring - let us know how it works out!
Best Wishes,
Peter
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Jason Daiger
Sent: Tuesday, June 13, 2006 5:19 PM
To: CFCDev@cfczone.org
Subject: RE: [CFCDev] Model or View?
Only if all
I generally have two lists (or a struct, whatever), RequiredFields and ErrorFields and I pass
this to the view. When you are displaying each form field, do a check against this set. For example,
if the field name is in the RequiredFields list, display an asterisk, if its in the ErrorFields
Are you using a bean to persist your form's submitted values?
What i do, cuz i'm a little intellectually lazy, like Ray, is to place
a validate function in my bean. Others abstract the validation to a
separate object, but i prefer having it in one package. It's just a
little easier for me to
Title: Message
Hi
Jason,
I
would take what Cody said and just expand on it a little.
Usually when you think about forms for editing objects, the most common
requirements are transformations, validations and calculations. Tranformation
might pull all the non-numerics from a phone field
lto:[EMAIL PROTECTED] On Behalf Of Peter BellSent:
Friday, June 09, 2006 2:10 PMTo:
CFCDev@cfczone.orgSubject: RE: [CFCDev] Model or
View?
Hi
Jason,
I
would take what Cody said and just expand on it a little.
Usually when you think about forms for editing objects, the most common
re
16 matches
Mail list logo
