Skip to main content

ColdFusion 10 : onAbort method in Application.cfc

I was experimenting with a new method 'onAbort' introduced in ColdFuion 10 which can be defined in an Application.cfc file. This method is invoked when cfabort is called. What if showerror attribute is also present in the cfabort tag? Would it still invoke the onAbort method and then onError? The onAbort method would be ignored and the onError method would be invoked. Even in a case wherein the onError method is not defined in Application.cfc, the onAbort method wouldn't be invoked. In this case the error message would be shown on the standard error template.

Application.cfc:
<cfcomponent> <cffunction name="onError" access="public" returntype="void" output="false" hint="I handle any uncaught exceptions."> <cfreturn/> </cffunction> <cffunction name="onAbort" access="public" returntype="void" hint="Hanldes Aborted request"> <cfargument type="String" name="requestPage" required=true/> <cfoutput> Request Page: #requestPage#</cfoutput> <!--- do stuff ---> </cffunction> </cfcomponent>
Now when the cfabort tag is executed, the onAbort method would be invoked. If the showerror attribute is present in the cfabort tag (<cfabort showerror="Error!!">), then the onError method would be invoked; ignoring the onAbort method.
Labels:

Comments

  1. David BoyerFebruary 28, 2012 at 9:49 PM

    Interesting, didn't know about the onAbort for CF10.  I'm curious though...  in CF9 onRequestEnd would execute after a CFAbort, is this still the case and does onAbort happen before or after the onRequestEnd (if it does)?

    See Ben's post on it for CF9 http://www.bennadel.com/blog/2221-CFAbort-And-OnRequestEnd-Behavior-In-ColdFusion-8-And-ColdFusion-9.htm

    ReplyDelete
  2. Sagar GanatraFebruary 28, 2012 at 10:18 PM

    David, thanks for bringing this up. In CF10, the onRequestEnd method will not be invoked when cfabort is executed. Also this method is not invoked when cflocation and cfcontent is executed.

    ReplyDelete
  3. Sagar GanatraFebruary 28, 2012 at 11:54 PM

    I've posted this change in behavior 
    http://www.sagarganatra.com/2012/02/coldfusion-10-onabort-and-onrequestend.html

    ReplyDelete

Post a Comment

Popular posts from this blog

File upload and Progress events with HTML5 XmlHttpRequest Level 2

The XmlHttpRequest Level 2 specification adds several enhancements to the XmlHttpRequest object. Last week I had blogged about cross-origin-requests and how it is different from Flash\Silverlight's approach .  With Level 2 specification one can upload the file to the server by passing the file object to the send method. In this post I'll try to explore uploading file using XmlHttpRequest 2 in conjunction with the progress events. I'll also provide a description on the new HTML5 tag -  progress which can be updated while the file is being uploaded to the server. And of course, some ColdFusion code that will show how the file is accepted and stored on the server directory.
18 comments
Read more

How to use the APP_INITIALIZER token to hook into the Angular bootstrap process

I've been building applications using Angular as a framework of choice for more than a year and this post is not about another React vs Angular or the quirks of each framework. Honestly, I like Angular and every day I discover something new which makes development easier and makes me look like a guy who built something very complex in a matter of hours which would've taken a long time to put the correct architecture in place if I had chosen a different framework. The first thing that I learned in Angular is the use of the APP_INITIALIZER token.
Post a Comment
Read more

On GraphQL and building an application using React Apollo

When I visualize building an application, I would think of using React and Redux on the front-end which talks to a set of RESTful services built with Node and Hapi (or Express). However, over a period of time, I've realized that this approach does not scale well when you add new features to the front-end. For example, consider a page that displays user information along with courses that a user has enrolled in. At a later point, you decide to add a section that displays popular book titles that one can view and purchase. If every entity is considered as a microservice then to get data from three different microservices would require three http  requests to be sent by the front-end app. The performance of the app would degrade with the increase in the number of http requests. I read about GraphQL and knew that it is an ideal way of building an app and I need not look forward to anything else. The GraphQL layer can be viewed as a facade which sits on top of your RESTful services o...
Post a Comment
Read more