Blog

Recently I did a webinar on Refactoring Legacy Code and the question came up about whether or not it was possible to use Coldbox with existing code without converting everything to a Coldbox module or making changes to the existing codebase. In the first installation in this series, we took a tour of the various elements which make up ColdBox. In the second installation, we looked at creating layouts, views, and routes in the main site. In this installation, we’re going to start incorporating our existing code base and do so using a module.

It's July 22nd... what has Ortus been publishing this week? We have the CFML News Podcast, some CFCasts and YouTube Videos, lots of Ortus and ITB Blog Posts. We have a lot more planned for next week as well.

Recently I did a webinar on Refactoring Legacy Code and the question came up about whether or not it was possible to use Coldbox with existing code without converting everything to a Coldbox module or making changes to the existing codebase. In the first installation in this series, we took a tour of the various elements which make up ColdBox. In this second installation, we are looking at creating layouts, views, and routes in the main site.

In this last session, Gavin was joined by Wil De Bruin. Wil De Bruin works a lot with CBValidation, contributed to the project, blogged a lot, and even presented at Into the Box in the past. They looked at different ways to validate your api input, your models, where to store your constraints, and helper methods to cut down on your API handler boilerplate. They discussed using validate() vs validateOrFail() and how you can make your own helper to make your api’s even more fluent. Join them as they validate the API Endpoints for Developer Feud Quiz API which Gavin presented at Adobe Developer Week!

It's July 15th... what has Ortus been publishing this week? We have the CFML News Podcast, some CFCasts and YouTube Videos, lots of Ortus and ITB Blog Posts. We have a lot more planned for next week as well.

Recently I did a webinar on Refactoring Legacy Code and the question came up about whether or not it was possible to use Coldbox with existing code without converting everything to a Coldbox module or making changes to the existing codebase. The answer is yes and there are many ways to do it. The method you choose depends on what the goals are for the conversion. Do you need to simply keep the exact same site but start moving toward Coldbox routes? Are you putting a new look to existing functionality but need to keep an existing site up and running in the meantime? Both these and several other scenarios are possible. We’ll take this blog series to walk through some of them.

Gavin appeared on the Online ColdFusion Meetup July 7th. The session the start of an Building an API Series, the recording and slides are now available.

In this next session, Gavin will be joined by Wil De Bruin. Wil De Bruin works a lot with CBValidation, contributed to the project, blogged a lot, and even presented at Into the Box in the past. They will discuss a lot of validation approaches, how and where to describe constraints, using validate() vs validateOrFail(), custom validators, and so much more. Join them as they validate the API Endpoints for Developer Feud Quiz API.

On July 29^th at 11:00 AM CDT, we are happy to announce the Dan Card will be presenting a follow up to his June webinar: Getting started with the Legacy Migration. Dan received some good questions, so July's Webinar: Legacy Migration Follow Up: Using Coldbox with an Existing Code Base with Dan Card. If you have a more traditional / legacy codebase, and are wanting to modernize with ColdBox, but don't know where to start, this webinar is just for you!

What has Ortus been publishing this week? We have the CFML News Podcast, some CFCasts and YouTube Videos, lots of Ortus and ITB Blog Posts. We have a lot more planned for next week as well.