Sumit,
We don't do any <cfdump> directly in the framework. It appears that
<cfdump> is the cause of the issue according to the thread. We just
pass up the cfcatch structure around and ultimately the cfcatch is put
in the Exception.cfc container.
We ship a simple and generic exception.cfm view with the Mach-II
skeleton. Yes, there is a dump there, but that file is not core to the
framework. It is part of your application and you are free to customize
at your will. If the <cfdump> is causing issues, then I would edit your
exception.cfm file with the workaround as suggested on that group thread.
Personally, I'd submit a bug to Adobe CF if this is an issue and get as
many people to vote up that issue. In the direct framework code all we
pass is the cfcatch so I don't believe this is not something we can fix
directly as it is a problem with the CFML engine itself. If passing
around a cfcatch is the problem, then something is intrinsically wrong
with Adobe CF9 and it is something they need to address immediately.
If you file a bug in the Adobe bug base, please post the link back here
so in the future people that stumble on this thread will be able to find
out the status of this defect in Adobe CF9.
Thanks for letting us know about the potential issue with CF9.
Best,
.Peter
Sumit Verma said the following on 02/03/10 11:58:
Hi Guys,
Exception handeling may need some changes to take care of CF ORM
issue:
http://groups.google.com/group/cf-orm-dev/browse_thread/thread/2c234c5f6af7b2dc?hl=en
Thanks,
Sumit
--
You received this message because you are subscribed to Mach-II for CFML list.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/mach-ii-for-coldfusion?hl=en
SVN: http://greatbiztoolsllc.svn.cvsdude.com/mach-ii/
Wiki / Documentation / Tickets:
http://greatbiztoolsllc.trac.cvsdude.com/mach-ii/