Blog

Brad Wood

September 19, 2012

Spread the word


Share your thoughts

 

In ColdBox, controllers or event handlers as we call them are defined as CFCs.  Part of the power of this is that you can share and extend code in your applications by simply extending one handler with another.  
 
Imagine a reporting framework where a number of reports will all have a criteria page, validation, execution, and export data action with most of the logic, views, layouts, and models the same between every report while still allowing for customizations on a per-report basis.
 
You could set up a base report handler that contained shared stuff like so:
 
component name="BaseReport" extends="coldbox.system.eventhandler" output="false"
{
  property name="ReportService" inject;
  
  public function init(Controller){
    super.init(arguments.controller);
    return this;
  }
  
  function criteria(Event, rc, prc){
    // Common Code
  }
  
  function execute(Event, rc, prc){
    // Common Code
  }
  
  function showResults(Event, rc, prc){
    // Common Code
  }
  
}
 
And then extend it per report with concrete handlers that add their own customizations:
 
 

component name="MyReport" extends="BaseReport" output="false"

{

  property name="myReportDAO" inject;

 

  function criteria(Event, rc, prc){

    super.criteria(Event, rc, prc);

    // Add in custom goodness for this report.

  }

}

 
More info on how amazing handlers are here: http://wiki.coldbox.org/wiki/EventHandlers.cfm
 
P.S. Remember, since ColdBox is chock full of choices, your event handlers don't have to eventually extend coldbox.system.eventhandler.  We could leave off the extends and the super.init() call on our BaseReport and WireBox will use virtual inheritance to ensure the handler has everything it needs.
 

 

Add Your Comment

Recent Entries

Copy of BoxLang AI 3.4 Blog Series Part 5 : Reasoning Without the Guesswork

Copy of BoxLang AI 3.4 Blog Series Part 5 : Reasoning Without the Guesswork

Reasoning-capable models have been usable in BoxLang AI for a while. params passes straight through to the provider body, so params: { thinking: { type: "enabled", budget_tokens: 10000 } } for Claude, or params: { reasoning_effort: "high" } for OpenAI, already reached the API. What never worked was reading the reasoning back. It was parsed out on arrival and silently dropped. In 3.4.0, that's fixed, and it's fixed the same way for every provider.

Luis Majano
Luis Majano
September 15, 2026
BoxLang 1.17 Series Part 4 : WriteDump Enhanced!

BoxLang 1.17 Series Part 4 : WriteDump Enhanced!

You call writeDump() on an ORM entity or a very rich class graph . The browser locks up. Thirty seconds later you get a page with forty thousand rows on it, you scroll for a while, you give up, and you go edit your code to dump a sub-key instead. Or worse, you crash the server.

Luis Majano
Luis Majano
September 11, 2026