Calling the experts
hi all,
i think might trying use cfrethrow in manner wasn't intended.
on our site have page tracking system call pagehistory. every page requested entered server scoped array when starts (i.e. in application.cfm), , array item updated @ end of request (onrequestend.cfm) end time , duration. has enabled write nifty activity monitor, real-time @ accessing our program, , pages accessed (plus form fields , query string used - essential investigative purposes). 1 drawback had when page errors out have open pagehistory record automatically close after hour. we've had trouble matching errors our page history when have been tasked fixing them. need page history enlighten how user got error - must have clicked on - can reproduce it.
so, thought put in error template ensure closes pagehistory record correctly. worked great. decided wanted see normal coldfusion error we've been seeing whenever error occurs (yes, normal cf error presented user - know that's bad, , why - let me client doesn't listen). thought <cfrethrow> accomplish task. added in, , yes did show original error on screen, didn't update server scoped page history array error status page, , error diagnostics.
if comment out cfrethrow , run test page intentional error, page history runs fine , updates array error, if put in, left open record - status doesn't changed.
it's rethrow performs "transaction rollback" taking out whatever changes cf code might have made... surely not, right?
any ideas appreciated.
swift
p.s. have attached errorhandler.cfm template. onrequestend contains pagehistory.cfm code include, among other things.
i think might trying use cfrethrow in manner wasn't intended.
on our site have page tracking system call pagehistory. every page requested entered server scoped array when starts (i.e. in application.cfm), , array item updated @ end of request (onrequestend.cfm) end time , duration. has enabled write nifty activity monitor, real-time @ accessing our program, , pages accessed (plus form fields , query string used - essential investigative purposes). 1 drawback had when page errors out have open pagehistory record automatically close after hour. we've had trouble matching errors our page history when have been tasked fixing them. need page history enlighten how user got error - must have clicked on - can reproduce it.
so, thought put in error template ensure closes pagehistory record correctly. worked great. decided wanted see normal coldfusion error we've been seeing whenever error occurs (yes, normal cf error presented user - know that's bad, , why - let me client doesn't listen). thought <cfrethrow> accomplish task. added in, , yes did show original error on screen, didn't update server scoped page history array error status page, , error diagnostics.
if comment out cfrethrow , run test page intentional error, page history runs fine , updates array error, if put in, left open record - status doesn't changed.
it's rethrow performs "transaction rollback" taking out whatever changes cf code might have made... surely not, right?
any ideas appreciated.
swift
p.s. have attached errorhandler.cfm template. onrequestend contains pagehistory.cfm code include, among other things.
i think cfrethrow tag has within cfcatch block?
i new cf appears way in livedocs.
good luck!
More discussions in Advanced Techniques
adobe
Comments
Post a Comment