> Well, I think I would put the email service CFC instance into the
> property space (in the emailService.configure() method) and then
> everything can access it easily using getProperty('emailService')
>
> If you have explicit (URL-based) requests that invoke the email
> service, you'll need a listener (manager) for it. Otherwise components
> can just use the property.
Ahh, good point didn't think to use the property space like that. So
essentially i'd use the setProperty() method inside my
emailService.configure() ?
Also, "everything" am I wrong to assume that only Listeners know about the
framework and that Managers,Beans,DAO,DTO's etc etc cannot.
Regards
Scott Barnes
To unsubscribe from this email please forward this email to [EMAIL PROTECTED]
This email message is confidential and may be privileged. If you are not the
intended recipient
please forward the email to [EMAIL PROTECTED] and delete the original.
ABN AMRO Morgans Limited and its associates hold or may hold securities in the
companies/trusts mentioned herein.
Any general advice included in this email has been prepared without taking into
account your objectives, financial situation or needs.
Before acting on the advice, you should consider its appropriateness or discuss
with one of our investment advisors.
ABN AMRO Morgans Limited (ABN 49 010 669 726 AFSL 235410) A Participant of ASX
Group.
A principal member of the Financial Planing Association.
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev'
in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported
by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at
[EMAIL PROTECTED]
