Blog

WireBox 1.7.0 Released!

Luis Majano July 10, 2013

Spread the word

Luis Majano

July 10, 2013

Spread the word


Share your thoughts

logo

We are proud to announce WireBox version 1.7.0. This is minor release that brings some important fixes but also some cool new enhancements. You can read in detail about this release in our What's new with WireBox 1.7.0.

The major enhancements of this release rely around the usage of closures for filtering and influencing mappings via mapDirectory(), ability to use any DSL with object providers, ability to use closures as providers, CacheBox and LogBox updates, new Java creation DSL namespace, and additional binder methods for tighter Java and JavaLoader integrations

 

 

Bugs Squashed

  • [WIREBOX-1] - ColdSpring2 parent bean factory adapter is not working due to mistype of adapter methods
  • [WIREBOX-8] - Binder implicit parentInjector setting is not being read and a parent injector is not being set.
  • [WIREBOX-9] - Problem shutting down CacheBox in injectors when it is not linked as it is pointing to ColdBox and not CacheBox

New Feature

  • [WIREBOX-4] - WireBox Provider To allow not only id but full dsl namespaces
  • [WIREBOX-10] - mapDirectory() new argument "influence" which can be a closure or UDF that receives the currently iteration binder and path so you can influence it.
  • [WIREBOX-11] - mapDirectory() new argument "filter" that can be a closure or UDF that accepts the incoming path and determines if it is processed or not by returning TRUE to process or FALSE to skip
  • [WIREBOX-12] - toProvider( closure/udf ) can now take in a closure or UDF that will produce the dependency
  • [WIREBOX-13] - Additional binder method and namespace for Java and JavaLoader

Resources:

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