I know that in 'a perfect world' a user should never technically see an error. But I know there is going to be some situations where it's infeasible, whether the error comes from use or development I'd like to give an appropriate error.
The project itself requires the errors to be i18n friendly. (So I've chosen xml for it's core). Using the error code attribute I can pass the errorcode to a cfc on the exception page.xmlsearch for the error code and return it's contents depending on the users locale. if there is no result, then use the 'standard' error message/ if the error type is request, .. then show it's standard page. That way if I can grab the error on the fly I have a judgement on how to present it to the user based on its content, and if it's unexpected... well I'm giving them the page they _were going to get anyways.
Couple of questions.
Am I overdoing it? ;)
When you nest calls in a cfc does the error always bubble up to the calling template or to the template from which the call was made.
Is there a known situation where this angle wouldn't work, or one that someone uses daily that handles this in a more intelligent fashion.
Sorry for the rambling post, long night... Born in Kansas City, Live north of Melbourne and I miss my football. (victim of latenight cable to catch a game)
Robby
_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail
----------------------------------------------------------
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).
