An Architect's View

To make it easier to manage collaboration on FW/1-related projects in future, several projects have now moved under a new FW/1 - Framework One - organization on Github. Your forks and watches should have been updated but if you have local clones of the old repos under my personal Github account, you'll want to update those. Here's the full list of Framework One projects:

• FW/1 - Framework One - simple MVC for CFML
• DI/1 - Inject One - simple Dependency Injection for CFML
• cfmljure - the magic bridge between CFML and Clojure
• FW/1 - Framework One - simple MVC for Clojure
• Leiningen project template for FW/1 - Framework One - for Clojure

If you were a collaborator on one of these projects before, you will no longer have commit access (because you were a collaborator directly on my repo). If you'd like to become a collaborating team member on one of these projects as part of the new organization, contact me directly to discuss that. I'd certainly like to see some of the regular contributors in the past become official "Team Framework One" members in the new organization!

Thank you to all the contributors who've helped get these projects to where they are now!

The seventh minor update in four months, this brings a number of bug fixes and enhancements to DI/1 - Inject One since the 0.4.0 release at the beginning of December, 2012:

• Fix optional constructor argument handling (with help from Marcin Szczepanski)
• Fix edge case bug in property / setter / accessor logic
• Setter metadata is cached, improving transient bean handling performance (Grant Shepert)
• Robustness fixes for file path handling and parent bean factory handling
• Add getVersion() API
• Addition of transientPattern configuration option (Matt Levine)

In addition, DI/1 has moved to the FW/1 - Framework One organization on Github. The old repo still exists under my account (and is an up-to-date fork), but you should watch / fork / contribute to the new repo going forward.

The bump in the version number is to indicate DI/1 is moving closer and closer to a 1.0 release. 0.4.0 brings a number of bug fixes (handling of optional constructor arguments, addAlias() bug, circular dependencies in properties). I think DI/1 is pretty close to feature complete - at least as far as my intended usage as a ColdSpring replacement is concerned - but I will make one more pass over its functionality shortly and open tickets for anything that I believe is missing. Please feel free to do the same. Once that pass is complete, a 1.0 Alpha will be declared.

You can find DI/1's issue tracker on Github. You can read more about DI/1 (and download it) on RIAForge (or from Github).

Thanx to John Whish (aliaspooryorik), DI/1 has a new singletonPattern option that allows you to specify which beans are singletons based on their name, regardless of the folder in which the CFC is found. See the DI/1 wiki for more information.

Things are moving along with DI/1 now that FW/1 2.0 is close to Gold status and you can download version 0.1.7 now. I'd still consider it pre-release but it's getting close to a true Alpha release with only one (hard) open issue to solve. Read on to see the recent changes...

[Read more →]

After a lot of things delayed the alpha release of FW/1 2.0, I've now found time to work on DI/1 again and get it into a usable shape. The idea is that you point DI/1 at one or more folders and it searches those folders for CFCs and builds a bean factory to manage them, all by convention (so no XML required!). DI/1 supports dependency injection, by name, through constructor argument, explicit setter methods and property declarations (with implicit setters enabled).

[Read more →]

Last year I'd talked about getting at least an alpha of FW/1 2.0 out the door by year end. It didn't happen. I was reminded of this on the FW/1 mailing list the other day and I provided a fairly detailed response on the plans for FW/1. I figured, since I haven't blogged about FW/1 in a while, I should post that roadmap response on my blog as well.

Is the 1.x version outdated?

No, the 1.x stream will continue to be supported. It will get bug fixes but it will not get new feature - except where I want to provide a migration path for people moving to 2.0 (for example, if I remove certain things marked deprecated in the docs, I'll provide the new API in a 1.x build to make it easier for folks to transition to 2.0). Expect at least a 1.3 version, possibly more. These versions will continue to support CFMX7+ as well as the older versions of Railo and OpenBD that 1.2 currently runs on.

Wasn't 2.0 imminent late last year?

Yes, FW/1 2.0 was very imminent at that point but work and then conference preparations overwhelmed me and it got put on the back burner for a while, along with DI/1.

Since a respite is coming in my day job (World Singles) - we're launching the second phase of our new platform soon - and I have a couple of months before the next conference, I expect to get back on top of FW/1 2.0 soon and once an alpha of that is available, I'll work on DI/1 to get an alpha of that out as well. And then I'll probably focus on cfmljure for a while, as we start to add Clojure to our production code base at work. And then it'll be beta versions of FW/1 2.0 and DI/1 and cfmljure, round and round, until they're all three "baked" and ready for official releases.

So DI/1 is coming?

Yes, DI/1 is still on my radar - I have plans for it at work so it will definitely happen! It's just been delayed (ironically, by the pressures of work). Since FW/1 2.0, DI/1 1.0 and cfmljure 1.0 will all be used in my production code at work, you can expect them to receive regular updates once I actually get to the alpha releases!

RTW - Reinventing The Wheel - is normally a bad thing. I'm said several times that the main reason we have no truly great open source software in ColdFusion is because when we see an open source project that doesn't do what we need, we go off and build our version, which we may or may not open source, instead of collaborating on the existing project to make it better.

[Read more →]