Blog

Brad Wood

August 23, 2012

Spread the word


Share your thoughts

The methods in your handlers (actions) have always accepted the "event" object, which is the request context for that event and contains things like the request collection and private request collection.

A common handler method used to look like this:

function index(event) {
  var rc = event.getCollection();
  var prc = event.getCollection(private=true);
  // Do Stuff
}


Remember, if you're using ColdBox 3.1 or higher, every action is now passed a reference to the request collection (rc) and private request collection (prc) as arguments so you don't have to get them yourself.

function index(event,rc,prc){
  rc.foo = "Isn't this convenient?";
  prc.bar = "Yes, yes it is.";
}


Remembering this tip can help clean up your code by omitting those uneccessary boilerplate lines of code to get the rc and prc.

More info here: http://wiki.coldbox.org/wiki/EventHandlers.cfm#Anatomy_of_an_Event_Handler_Action

Add Your Comment

Recent Entries

Building Native CLI Apps with MatchBox & Native Fusion

Building Native CLI Apps with MatchBox & Native Fusion

MatchBox makes BoxLang practical for a classic deployment target: the single-file command-line application.

The MatchBox open beta is available at https://github.com/ortus-boxlang/matchbox.

With the MatchBox native target, you can compile a .bxs script into a standalone executable for macOS, Linux, or Windows. The generated binary includes the MatchBox VM core and your compiled BoxLang bytecode. It does not require a JVM, a separate MatchBox install, or any runtime on the target machine.

Jacob Beers
Jacob Beers
July 14, 2026