Ok with that, should when an error is thrown by the CFC, throw out to CF via cfthrow or should it contain it's own exception handling and return error values to the developer who is using the CFC?
For an example when a user does not follow directions on how to use the CFC properly by passing it the correct arguments. Such as if you have a CFC that does DB access using cfquery and it needs the DSN var that is normally in the Request scope of the application the CFC resides in. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Thomas Chiverton Sent: Wednesday, July 16, 2003 10:57 AM To: [EMAIL PROTECTED] Subject: Re: [CFCDev] Stand-Alone CFCs? On Wednesday 16 Jul 2003 15:50 pm, Bryan F. Hogan wrote: > Is it true that a CFC should not reference shared scope variables. And that > all variables needed for the operation of the CFC should be entered as > arguments? That is the best way to abstract your objects, so you can share them more easily arround your applications. > If this is true and a CFC should be a tree in the desert, is using CFFILE > tags in a CFC bad practice also? Not entirly. It may make sense for it to reference an external configuration file if it has a complex configuration, or it may need to bring in external images or something. Just make sure the path to the file is dynamic (take it as an argument) and all should be well. -- Thomas C Advanced ColdFusion Programmer HANDLE WITH EXTREME CARE: This Email Contains Minute Electrically Charged Particles Moving at Velocities in Excess of Five Hundred Million Miles Per Hour. PLEASE ALSO NOTE: I don't speak for the company that sent this. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
