I think that a standard is arising on the way a method is injected with a request bus. My naming was requestContext and I believe mach-ii and fusebox use both event. I think it would be benefitial for developers for me to change this to event. What are your thoughts on this? This would help if a developer wants to switch from one framework to another or doing a transition, if some of the similar elements shared in an MVC framework can remain the same. I am for changing it to event, but I would like to know you opinions?
Blog
Recent Entries
BoxLang CouchBase Module: Enterprise Caching, Distributed Locking, and AI Vector Memory
We're thrilled to announce the release of bx-couchbase v1.0, bringing enterprise-grade Couchbase integration to the BoxLang ecosystem. This powerful module combines high-performance distributed caching with cutting-edge AI capabilities, enabling developers to build scalable, intelligent applications with ease.
Luis Majano
Luis Majano
December
05,
2025
BoxLang v1.8.0 : Revolutionary HTTP Client, SOAP Integration, and Production-Grade Stability
The BoxLang team is excited to announce BoxLang 1.8.0, a massive release that revolutionizes HTTP capabilities, introduces comprehensive SOAP/WSDL integration, and delivers over 100 critical bug fixes for production-grade stability. This release focuses on modern web application development with fluent APIs, streaming support, persistent connection management, and extensive CFML compatibility improvements.
Luis Majano
Luis Majano
December
05,
2025
Ortus & BoxLang November Recap 2025
November 2025 was a big month at Ortus. BoxLang 1.7.0 arrived with real-time streaming, distributed caching, and faster compiler internals. ColdBox gained a cleaner debugging experience with full Whoops support, while CBWIRE 5 launched with stronger security, smarter lifecycles, and easier uploads.
Victor Campos
Victor Campos
December
02,
2025
Add Your Comment
(5)
Feb 27, 2007 14:48:06 UTC
by Sana
Hi Luis, This makes perfect sense, should have some compatibility to other frameworks, at-least vocabulary should be same, so new developers adopt more easily.
Feb 27, 2007 16:20:13 UTC
by Sami Hoda
Can this be a customizable parameter instead?
Feb 27, 2007 18:07:03 UTC
by Luis Majano
I have been going over this and I think the best way is to just call the method and pass the argument. It would then be up to the developer to name the argument. However, the type of the argument will always be: coldbox.system.beans.requestContext How does this sound?
Feb 27, 2007 19:09:58 UTC
by Sami Hoda
I suppose that works. Whenever there is a chance for flexibility, I'm for it.
Mar 05, 2007 19:19:15 UTC
by tony petruzzi
Actually most of the other frameworks let you change the name to whatever you want, they just use event as the default. But you are correct when saying that this would make it alot easier to transition from one framework to another. BTW great work. ColdBox is getting more and more attention lately. I haven't heard anything coming out of the Model-Glue camp.