Application Lifecycle

The previous lesson covered onApplicationStart, onRequestStart/onRequest, and onError individually. This lesson is about the bigger picture: the fixed order all of Application.cfc's event methods fire in, plus the four events that lesson didn't cover — onRequestEnd, onAbort, onCFCRequest, and onServerStart.

Learning Objectives

After completing this lesson, you'll be able to:

• Name all the Application.cfc lifecycle events in the order they fire.
• Write an onRequestEnd method for cleanup or footer-style logic.
• Explain when onAbort runs instead of onRequestEnd.
• Explain why onServerStart isn't actually a method of Application.cfc.

The Full Event List

The Normal Request Flow

onRequestEnd — Cleanup After Everything Else Runs

onRequestEnd fires after all the page's own CFML code has finished, but while the page context is still available — useful for performance logging or dynamic footer content.

<cfscript>

function onRequestEnd(targetPage) {
    if (structKeyExists(session, "username")) {
        include "authuserfooter.cfm";
    } else {
        include "noauthuserfooter.cfm";
    }
}

</cfscript>

<cffunction name="onRequestEnd" returnType="void">
    <cfargument name="targetPage" type="string" required="true">
    <cfif structKeyExists(session, "username")>
        <cfinclude template="authuserfooter.cfm">
    <cfelse>
        <cfinclude template="noauthuserfooter.cfm">
    </cfif>
</cffunction>

onAbort — When a Request Gets Cut Short

<cfscript>

function onAbort(targetPage) {
    writeLog(file = "myapp", type = "information", text = "Request aborted: " & targetPage);
}

</cfscript>

<cffunction name="onAbort" returnType="void">
    <cfargument name="targetPage" type="string" required="true">
    <cflog file="myapp" type="information" text="Request aborted: #arguments.targetPage#">
</cffunction>

onCFCRequest — Direct CFC Calls (Ajax, Web Services)

When a CFC is called directly over HTTP (rather than through a normal .cfm page), onCFCRequest fires instead of onRequestStart/onRequest — useful for centralizing logging or validation across every CFC endpoint.

<cfscript>

function onCFCRequest(cfcname, method, args) {
    writeLog(file = "myapp", type = "information", text = "CFC call: " & cfcname & "." & method);
    return invoke(cfcname, method, args);
}

</cfscript>

<cffunction name="onCFCRequest" returnType="void">
    <cfargument name="cfcname" type="string" required="true">
    <cfargument name="method" type="string" required="true">
    <cfargument name="args" type="struct" required="true">
    <cflog file="myapp" type="information" text="CFC call: #arguments.cfcname#.#arguments.method#">
    <cfinvoke component="#arguments.cfcname#" method="#arguments.method#" returnVariable="result" argumentCollection="#arguments.args#">
</cffunction>

onServerStart Isn't Actually Part of Application.cfc

Despite being listed alongside the other lifecycle events, onServerStart doesn't live in Application.cfc at all — it lives in a separate file, Server.cfc, in the web root (or a custom path set in the ColdFusion Administrator). It's disabled by default and has to be turned on explicitly.

It also behaves differently: it takes no arguments, is the only method in Server.cfc, runs once when the ColdFusion server itself starts (independent of any specific application), and can't access the Application or Request scopes — there isn't one yet at that point.

Common Beginner Mistakes

Best Practices

• Don't put logic in onRequestEnd that absolutely must run even when a page redirects or aborts — use onAbort for that, or a pattern that doesn't depend on either.
• Keep onCFCRequest lightweight (logging, basic validation) — it sits in front of every direct CFC call, so slow code there slows down all of them.
• Only enable Server.cfc's onServerStart for genuinely application-independent setup (scheduler configuration, logging setup) — not application-specific logic.

Interview Questions

Summary

In this lesson, you covered the full, fixed order of Application.cfc's lifecycle events, wrote onRequestEnd and onAbort methods, covered onCFCRequest for direct CFC calls, and learned that onServerStart actually belongs to a separate Server.cfc file.

What's Next?

The next page is a dedicated interview-prep companion for everything covered in this lesson and the last one — the specific questions people actually get asked about Application.cfc, each with a real-world analogy.