that's helpful.
/charlie
-Original Message-
From: cfaussie@googlegroups.com [mailto:cfaussie@googlegroups.com] On
Behalf Of AJ Dyka
Sent: Tuesday, June 07, 2011 10:00 PM
To: cfaussie
Subject: [cfaussie] Re: Catching cfcomponent extends errors
True, however I want to fix the mapping
On Thu, Jun 9, 2011 at 10:13 AM, charlie arehart
charlie_li...@carehart.org wrote:
AJ, I think Kai and Mark may have been on the right track: with CFERROR
(which would typically be setup at the application level, in
application.cfm) or the onerror method of application.cfc, I'm pretty sure
] Re: Catching cfcomponent extends errors
On Thu, Jun 9, 2011 at 10:13 AM, charlie arehart
charlie_li...@carehart.org wrote:
AJ, I think Kai and Mark may have been on the right track: with
CFERROR
(which would typically be setup at the application level, in
application.cfm) or the onerror
Not what I was hoping for :-/ Oh well ...
I think that restructuring the relationship between by CFCs will be
the only solution but it's not something I'm willing to think about at
the moment!
Thanks anyway :)
On Jun 8, 10:30 am, Sean Corfield seancorfi...@gmail.com wrote:
This is a
True, however I want to fix the mapping not just hide the error ...
perhaps I can write my own error template which checks the mappings
and fixes them if they're missing? That could work for me ...
On Jun 8, 11:05 am, MrBuzzy mrbu...@gmail.com wrote:
But using a global error handler will enable
