Blog

Luis Majano

December 06, 2011

Spread the word


Share your thoughts

Today we are releasing a free chapter of our CBOX-202: WireBox Dependency Injection & AOP course to the ColdFusion community.  The chapter is an introduction of dependency injection and inversion of control.

Download Here: http://ortus-public.s3.amazonaws.com/cbox202-unit1-3.pdf

We cannot stress the value of using a DI framework in your Object Oriented ColdFusion applications.  There are INCREDIBLE amount of benefits from using a DI framework that you should definitely check this out.  Even if you have never used DI or cared about it, we believe it is fundamental to building sustainable OO ColdFusion applications.  Throughout our experience either in the open source arena or commercial arena, we still see a lack of usage of DI principles in ColdFusion applications and we would like to contribute in terms of education so this topic can be demystified and applied.

There are currently two incredible DI and AOP frameworks for ColdFusion:

Of course, we would recommend WireBox as it is our product.  However, needless to say both libraries are great, proven and very compatible with each other.  The crux of this post is not WireBox is better, or ColdSpring is better, but that using a DI is better.  Forget about how you will implement it, just DO IT!

Anyways, I am incredibly passionate about not only our products, but about ColdFusion and education.  I welcome your thoughts, suggestions and comments.

Add Your Comment

Recent Entries

MatchBox and WebAssembly: Running BoxLang in the Browser and at the Edge

MatchBox and WebAssembly: Running BoxLang in the Browser and at the Edge

The MatchBox open beta is live at https://boxlang.ortusbooks.com/boxlang-framework/matchbox, and it brings something genuinely new to the BoxLang ecosystem: a path into WebAssembly.

That means BoxLang code can now move into browser applications, static-site deployments, edge runtimes, and WASI-style containers - without requiring a JVM. The feature is still beta, but the core direction is already useful: write BoxLang, compile it with MatchBox, and ship the generated WASM artifact to wherever a small portable runtime makes sense.

Jacob Beers
Jacob Beers
June 04, 2026