Mach-II 1.5 - List of Officially Deprecated Elements

In Mach-II 1.5, we wanted to remind everyone about the elements that are officially deprecated.  Please take this list seriously as we plan to remove all of the elements in this list in Mach-II 2.0.  Unlike in Java, where elements remain in the virtual machine despite being deprecated many years ago, the items in this list will go away in Mach-II 2.0.

Read more to check out what is going  to removed from the framework core in Mach-II 2.0 which is slated for alpha release end of Q1 or early Q2 2008.

Old Invokers

CFCInvoker_Event.cfc and CFCInvoker_EventArgs.cfc were officially deprecated in Mach-II 1.1.0.  Please use the new invokers.  If you do not know what a listener invoker is, then you are not using them and have nothing to worry about.

ContentKey and ResultKey

 In conjunction with the old invokers, ContentKey and ResultKey were deprecated in Mach-II 1.1.0 although we did not preach this deprecation in the documentation fully.  Some of our planned features such as caching and some of the other unannounced features in 2.0 rely on using ContentArg and ResultArg.  Please develop all new applications with using ContentArg and ResultArg.

EventBean Filter

This filter is bundled in the core framework, but it will be deprecated in Mach-II 1.5 as it was replaced by the event-bean command in Mach-II 1.0.6.

HasParameter() in BaseComponent

HasParameter() is a function available in the BaseComponent, which is in turn inheirited by all listeners, filters, properties and plugins.  In an effort to clean up the API and keep consistent method names, please use isParameterDefined() instead.  HasParameter() was officially deprecated in Mach-II 1.1.0.

HasProperty() in PropertyManager

HsProperty() is a function available in the PropertyManager. In an effort to clean up the API and keep consistent method names, please use isPropertyDefined() instead. HasProperty() was officially deprecated in Mach-II 1.1.0.

1 Comment  |  1 Trackback  |  Mach-II 1.5  |  Send
Posted 7/5/07 @ 5:10 PM by Peter J. Farrell

Comments

It's great to see this list!

I know how hard it is to keep a framework moving forward while still supporting all of the legacy baggage. These all seem like very fair deprecations to me and perfectly reasonable to remove them in a major release like 2.0.

So far with Fusebox, I've only removed two features: direct access to XML fragments inside the framework (a bad architecture) and assertions (which no one used - and Fusebox 5.5 adds back in a more powerful plugin / lexicon architecture). Lots of things have already been deprecated tho', some dating back to Fusebox 4.1, so I added a "strict" mode that flags the use of deprecated features as an aid to migration.

I'm assuming you'll add lots of "angry logging" for deprecated features in 1.5 so folks can easily spot they are using features that will go away?

Posted by Sean Corfield at 7/10/07 3:08 PM