Question that is, by proxy, CFC related: I am in the process of creating an application that CFTHROWS several different types of custom exceptions in several parts of the application. They include:
1) Form validation errors 2) Business logic validation errors 3) Database errors 4) Unexpected application errors......plus a few more Each error type differs slightly in the type of context-sensitive "custom" information that is added to the CFCATCH struct when the exception in caught. Form validation errors and business logic errors often include a "hint" that is added in the catch block, then read and output by the UI layer. Other errors caught in the application have other "custom" data items added used for logging and debugging. The end result is that various parts of the application "listen" for specific types of errors and "process" them when they're found. ** The problem is there is no consistency between the error data structures, how the data is analyzed, and how the application decides what to do with the error information. ** So, the question: has anyone done a Java-style system of using something like ErrorManager.cfc/Error.cfc, where each exception creates a new error object, and the ErrorManager.cfc is queried to receive error information? Not looking to copy anyone's code here - just some guidance on a solid approach! Much appreciated! -- Alex Sherwood PHS Collection Agency [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]
