|
| 1 | +--- |
| 2 | +description: April 27, 2025 |
| 3 | +--- |
| 4 | + |
| 5 | +# What's New With 7.4.0 |
| 6 | + |
| 7 | +Welcome to ColdBox 7.4.0, our last planned release for the 7.x series before our 8.x series starts. Let's review the major updates of these release. |
| 8 | + |
| 9 | + |
| 10 | + |
| 11 | +## ColdBox Updates |
| 12 | + |
| 13 | +<figure><img src="../../.gitbook/assets/logo-gradient-dark.png" alt=""><figcaption><p>www.boxlang.io</p></figcaption></figure> |
| 14 | + |
| 15 | +### BoxLang Support |
| 16 | + |
| 17 | +With the latest updates, ColdBox extends its capabilities to support the development of entire applications using BoxLang exclusively. This enhancement allows developers to leverage the full power and modern syntax of BoxLang, streamlining the development process and adopting current best practices.  |
| 18 | + |
| 19 | +For those who prefer a gradual transition, ColdBox offers the flexibility to integrate BoxLang within existing ColdFusion Markup Language (CFML) applications. Consequently, developers can choose to write components, handlers, views, and models using either BoxLang, CFML, or a combination of both. This dual-support approach not only facilitates a seamless transition for applications migrating from CFML to BoxLang but also enables new projects to be crafted entirely in the more modern and robust BoxLang environment. |
| 20 | + |
| 21 | +There is nothing you do in terms of settings or configuration. ColdBox will detect if your handlers, interceptors, models and views are in BoxLang or CFML and act accordingly and seamlessly. |
| 22 | + |
| 23 | +### BoxLang Template |
| 24 | + |
| 25 | +You also now have a `bx-default` application template you can use to build your applications with. You can find it here: [https://github.com/coldbox-templates/bx-default](https://github.com/coldbox-templates/bx-default). You can use the `coldbox-cli` to get started with pure BoxLang apps with a simple command: |
| 26 | + |
| 27 | +```bash |
| 28 | +coldbox create app skeleton=boxlang |
| 29 | +``` |
| 30 | + |
| 31 | +More templates are coming soon. |
| 32 | + |
| 33 | +### ColdBox CLI |
| 34 | + |
| 35 | +The entire ColdBox CLI has been updated and all commands now have a new `boxlang` boolean argument. You can either pass it or it will try to detect if your server of choice is BoxLang or if you have a `language: "BoxLang"` key in your `box.json`. If so, then it will treat your project as a BoxLang language and all generations will be BoxLang classes or templates. |
| 36 | + |
| 37 | +```bash |
| 38 | +coldbox create handler main --boxlang |
| 39 | +``` |
| 40 | + |
| 41 | +You can also tell the ColdBox and TestBox CLI that your application is a pure BoxLang application by using the new `language` setting in your `box.json`. |
| 42 | + |
| 43 | +```json5 |
| 44 | +{ |
| 45 | + |
| 46 | + "language" : "boxlang" |
| 47 | + |
| 48 | +} |
| 49 | +``` |
| 50 | + |
| 51 | +## CacheBox Updates |
| 52 | + |
| 53 | +### DiskStore Rewrite |
| 54 | + |
| 55 | +The entire `DiskStore` has been rewritten to include better performance but more importantly to be able to be used concurrently and on distributed network drives. It no longer relies on in-memory indexes and each store on each cluster node can rebuild itself. |
| 56 | + |
| 57 | +### BoxLang Providers |
| 58 | + |
| 59 | +If you are migrating your ColdBox applications then you will need to update your Lucee/CF Providers to use the BoxLang ones: |
| 60 | + |
| 61 | +| Lucee | Adobe | BoxLang Equivalent | |
| 62 | +| -------------------- | ----------------- | ---------------------- | |
| 63 | +| LuceeProvider | CFProvider | BoxLangProvider | |
| 64 | +| LuceeColdboxProvider | CFColdBoxProvider | BoxLangColdBoxProvider | |
| 65 | + |
| 66 | +### Memory Indexers |
| 67 | + |
| 68 | +Memory indexers have also been rewritten to improve stability on clustered servers and to avoid null issues and double map tracking. |
| 69 | + |
| 70 | + |
| 71 | + |
| 72 | +## LogBox Upates |
| 73 | + |
| 74 | +Rollling file threads had an bad setting and they would be running on a 1 millisecond timer. This not only has been mitigated, but also made it configurable via the `rotatorSchedulerMinutes` property on the appender. |
| 75 | + |
| 76 | + |
| 77 | + |
| 78 | +## WireBox Updates |
| 79 | + |
| 80 | +WireBox now completely talks BoxLang and CMFL. Giving it the ability to inject, build and compose objects of either language. |
| 81 | + |
| 82 | + |
| 83 | + |
| 84 | +## Release Notes |
| 85 | + |
| 86 | +{% tabs %} |
| 87 | +{% tab title="ColdBox HMVC" %} |
| 88 | +### Improvement |
| 89 | + |
| 90 | +[COLDBOX-1286](https://ortussolutions.atlassian.net/browse/COLDBOX-1286) Make sure global scheduler is loaded after modules load. |
| 91 | + |
| 92 | +[COLDBOX-1287](https://ortussolutions.atlassian.net/browse/COLDBOX-1287) If running scheduled tasks manually with a \`force\` then do not set the next run since this is a forced run. |
| 93 | + |
| 94 | +[COLDBOX-1288](https://ortussolutions.atlassian.net/browse/COLDBOX-1288) Allow Disabling of PrettyJson in Log Output |
| 95 | + |
| 96 | +[COLDBOX-1294](https://ortussolutions.atlassian.net/browse/COLDBOX-1294) Call \`reset()\` when testing and unloadColdbox is true in the \`afterTests()\` to make sure the reset procedures are done, not only the shutdown. |
| 97 | + |
| 98 | +[COLDBOX-1305](https://ortussolutions.atlassian.net/browse/COLDBOX-1305) Improvement: Update Config Seeding to Include Original Module Settings |
| 99 | + |
| 100 | +#### New Feature |
| 101 | + |
| 102 | +[COLDBOX-1285](https://ortussolutions.atlassian.net/browse/COLDBOX-1285) BoxLang Support so you can write your ColdBox apps in BoxLang |
| 103 | + |
| 104 | +[COLDBOX-1296](https://ortussolutions.atlassian.net/browse/COLDBOX-1296) New flow peek() method to do fluent peeks in objects |
| 105 | + |
| 106 | +[COLDBOX-1297](https://ortussolutions.atlassian.net/browse/COLDBOX-1297) Schedulers now have a startupTask( task ) to dynamically startup a task by name or task object |
| 107 | + |
| 108 | +[COLDBOX-1306](https://ortussolutions.atlassian.net/browse/COLDBOX-1306) Better tracking of status code and text on the request context so integration tests are not corrupted by response commitment: getStatusCode(), getStatusText() accessors |
| 109 | + |
| 110 | +#### Bug |
| 111 | + |
| 112 | +[COLDBOX-1280](https://ortussolutions.atlassian.net/browse/COLDBOX-1280) coldbox.system.cache.policies.LRU cleanup errors |
| 113 | + |
| 114 | +[COLDBOX-1281](https://ortussolutions.atlassian.net/browse/COLDBOX-1281) DateTimeHelper.validateTime Regression |
| 115 | + |
| 116 | +[COLDBOX-1282](https://ortussolutions.atlassian.net/browse/COLDBOX-1282) ScheduledTasks Bug - java.util.concurrent.TimeUnit type error |
| 117 | + |
| 118 | +[COLDBOX-1289](https://ortussolutions.atlassian.net/browse/COLDBOX-1289) Directory Helper Logic in Renderer.cfc is Incorrect and Generates Bad Path On Windows |
| 119 | + |
| 120 | +[COLDBOX-1295](https://ortussolutions.atlassian.net/browse/COLDBOX-1295) Dumps in BugReport.cfm need top attributes |
| 121 | + |
| 122 | +[COLDBOX-1304](https://ortussolutions.atlassian.net/browse/COLDBOX-1304) thisLocationToken is not var scoped |
| 123 | + |
| 124 | +[COLDBOX-1311](https://ortussolutions.atlassian.net/browse/COLDBOX-1311) Remove direct calls to the servlet response.setStatus( int, String ) methods due to jakarta removing statusText |
| 125 | + |
| 126 | +[COLDBOX-1317](https://ortussolutions.atlassian.net/browse/COLDBOX-1317) ACF 2025 has removed htmlEditFormat |
| 127 | + |
| 128 | +[COLDBOX-1326](https://ortussolutions.atlassian.net/browse/COLDBOX-1326) populator discover entity name not accouting for missing entityname |
| 129 | + |
| 130 | +[COLDBOX-1327](https://ortussolutions.atlassian.net/browse/COLDBOX-1327) \`layoutLocations\` variable error when using event.noLayout() |
| 131 | +{% endtab %} |
| 132 | + |
| 133 | +{% tab title="CacheBox" %} |
| 134 | +### New Feature |
| 135 | + |
| 136 | +[CACHEBOX-87](https://ortussolutions.atlassian.net/browse/CACHEBOX-87) BoxLang Providers |
| 137 | + |
| 138 | +[CACHEBOX-88](https://ortussolutions.atlassian.net/browse/CACHEBOX-88) New approach for indexing objects on object stores to allow for concurrency and without separating indexers |
| 139 | + |
| 140 | +### Bug |
| 141 | + |
| 142 | +[CACHEBOX-86](https://ortussolutions.atlassian.net/browse/CACHEBOX-86) JDBCStore has double now overrides when doing insert/updates on caching. Remove one of them |
| 143 | + |
| 144 | +### Improvement |
| 145 | + |
| 146 | +[CACHEBOX-42](https://ortussolutions.atlassian.net/browse/CACHEBOX-42) Rewrite CacheBox DiskStore to not rely on in-memory indexer |
| 147 | +{% endtab %} |
| 148 | + |
| 149 | +{% tab title="LogBox" %} |
| 150 | +### Bug |
| 151 | + |
| 152 | +[LOGBOX-81](https://ortussolutions.atlassian.net/browse/LOGBOX-81) Make the Rolling File Appender rotator task timer configurable: rotatorSchedulerMinutes property |
| 153 | + |
| 154 | +[LOGBOX-82](https://ortussolutions.atlassian.net/browse/LOGBOX-82) LogBox Rolling file threads rotator running on an insane millisecond timer instead of minutes |
| 155 | +{% endtab %} |
| 156 | + |
| 157 | +{% tab title="WireBox" %} |
| 158 | +### Bug |
| 159 | + |
| 160 | +[WIREBOX-155](https://ortussolutions.atlassian.net/browse/WIREBOX-155) ExceptionBean is referenced but not shipped with Standalone install |
| 161 | +{% endtab %} |
| 162 | +{% endtabs %} |
0 commit comments