Try the InteriorDecorator. It has better "pattern matching" and helps
you blend your properties and methods in a more tasteful manner.
--
Alex
Dawson, Michael wrote:
I need to add some common functionality to a CFC I just created.
Basically, I want to add a few methods that perform some
validation-related tasks. These functions don't actually perform the
validate, but they will return status information based on the
validation that will have been performed.
My CFC is named ClassmateFormDataAnalyzer. This is an object with
string-type properties and a validation method.
When I find an error or missing property, I want to add a message to a
queue so I can display all of the messages at one time when I reload the
form for re-editing.
Is this the correct situation to extend a base CFC?
I was thinking of creating a CFC named "FormDataAnalyzer" that is
extended by the specialized CFCs for each form.
Some of the common methods would be:
hasErrors
getErrors
Is this the proper method?
Thanks
M!ke
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject of the
email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
(www.cfxhosting.com).
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
