On Wednesday 17 Sep 2003 21:02 pm, Adam Wayne Lehman wrote: > Being able to write custom error messages which says what method threw > the error! :nods I asked about this too.
I'm intergrating log4cf into all out CFC's, and to this end have written a 'log' cfc that can be called on CFC create/destroy, and method start/end. The trouble was the method had to pass it's own name as a method into the call to the log CFC. This seemed a bit pointless, it felt wrong you couldn't determine it yourself. I wunder if you can get the arguments too... -- Tom Chiverton (sorry 'bout sig.) Advanced ColdFusion Programmer Tel: +44(0)1749 834997 email: [EMAIL PROTECTED] BlueFinger Limited Underwood Business Park Wookey Hole Road, WELLS. BA5 1AF Tel: +44 (0)1749 834900 Fax: +44 (0)1749 834901 web: www.bluefinger.com Company Reg No: 4209395 Registered Office: 2 Temple Back East, Temple Quay, BRISTOL. BS1 6EG. *** This E-mail contains confidential information for the addressee only. If you are not the intended recipient, please notify us immediately. You should not use, disclose, distribute or copy this communication if received in error. No binding contract will result from this e-mail until such time as a written document is signed on behalf of the company. BlueFinger Limited cannot accept responsibility for the completeness or accuracy of this message as it has been transmitted over public networks.*** ---------------------------------------------------------- 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). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
