At 02:41 PM 5/10/2004, you wrote: >On May 10, 2004, at 11:35 AM, Alexander Sherwood wrote: >>The reason is this: The CFC can be invoked from a Mach-II like framework, OR >>remotely, where the context of the framework doesn't exist. > >Well, either your CFC is a Listener (in which case it shouldn't be used outside the >framework) or it is a business object (in which case it shouldn't know anything at >all about the framework anyway). Sounds like you need to decouple your CFC from the >framework more cleanly. Does that help?
Yea. It's definitely a listener. What would you suggest in this case? Should I create a CFC that wraps the calls to the listener and henceforth can customize the exception handling, or create an event in the Framework that handles the calls?! Thanks! >Regards, >Sean > >---------------------------------------------------------- >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 www.mail-archive.com/[EMAIL PROTECTED] ---------------------------------------------------------- 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 www.mail-archive.com/[EMAIL PROTECTED]
