Note: This blog post is from 2016. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.Continuing a series of posts I started last week on ColdFusion (2016 Release), aka CF 2016, I'd like to highlight the items that Adobe has chosen to deprecate and/or declare as "no longer supported", as of CF 2016.
(Note that for now, nothing is "obsoleted" or "removed" in CF2016, so this is just about our being made to know that certain features that DO work now in CF 2016 may NOT in future releases and won't be receiving any additions, enhancements, or modifications. )
While some of these features listed as deprecated will be things that most won't miss (and some may even wonder why they weren't deprecated sooner), some of the features listed as deprecated may really surprise some folks, as I'd not heard discussion of their deprecation myself until finding them discussed in the CF docs.
Some introductory observations
Before I start listing them, let me note that I am indeed simply sharing info that is readily available in the docs, but first of all, that page lists not only what's deprecated in 2016, but indeed what's been deprecated in all releases back to CF 6 (CFMX). I'm drawing out here ONLY what's deprecated in CF 2016. Second, they are offered in that docs page in a seemingly random order. I present them here in what I think may be more logical groupings.
Also note from that document that Adobe has for the first time created yet another subset of deprecation, as in "deprecated AND unsupported". The difference in the latter is that they are also declaring that they will not be making any bugfixes to them (during the CF 2016 release lifetime), except perhaps for security reasons. Some things that are "deprecated and unsupported" as of CF2016 were already deprecated in CF11 or earlier. I'll break out separately also, below.
With that, let's proceed to the 3 groups of deprecations.
1) Language/tags/functions deprecated in 2016Following are deprecated features which are enabled through CFML code:
- cfchart- format flash
- cffileupload Flash component
- UI Tags based on YUI toolkit - cftree, cfcalendar, cfautosuggest, cfmenu*
2) CF Admin features deprecated
Following are deprecated features which are either only used via the CF Administrator or are related to it, or support language features though it:
- Event gateway - Jabber, Flash Media server
- Server Manager
Server Monitor(Adobe subsequently said that the monitor would NOT be deprecated)
- System Probes
And to others who are surprised to hear that the CF Server Monitor is deprecated, so was I. Granted, it's never changed from being Flash-based, but I thought at some point Adobe would just rewrite it as HTML5. That now seems not to be in the future. (Adobe subsequently said that the monitor would NOT be deprecated)
(Folks should definitely check out FusionReactor, the third-party CF server monitor, which HAS been using HTML5 for a few years, and which can in fact monitor not just CF but Railo/Lucee, BlueDragon, OpenBlueDragon, and indeed any JAva app server, like Tomcat, JBoss, Glassfish, Jetty, etc.)
3) Other features deprecated
Finally, following is a deprecated features which is neither specific to language/CFML or the CF Admin:
- Report Builder*
The Report Builder is another item I was a bit surprised to learn was deprecated (and "no longer supported"), though I do of course understand it's not been updated in a long time, and many never got to using it, though I know some folks who do and will be surprised to hear of this. I'll talk about a few such surprises to me (and perhaps some other folks) in the conclusion below.
Features marked "deprecated and unsupported" in CF2016, but deprecated already previously
The following were all already deprecated in CF11, but they are also now marked as "unsupported" in CF 2016, so they won't receive bug fixes (eccept perhaps for security reasons):
- AIR integration
- CF actionscript functions (CF.query, CF.http, etc.)
- cfdocument format="flashpaper"
- CORBA integration
- Flash forms
- LCDS integration
- cfpresentation flash presentations
- cfslider/cftree/cfgrid, if using format="applet"
- xml forms
Conclusion: no "obsolete/removed" features, yet perhaps surprises
In conclusion, let me repeat that none of the features listed above are "obsoleted" or "removed" in CF 2016. They are simply deprecated, indicating that they will not be updates and should NOT be expected to be in future releases. And in some cases they are "deprecated and unsupported", which will receive no bugfixes, except perhaps for security reasons.
Even so, there may be many things that some are "glad to see go", such as all the things related to Flash or applets or UI components.
Still, a couple of other things may at least surprise those who perhaps DID still use them, like the Report Builder (thought it's not been updated in years), the System Probes and the Server Manager (though many never even knew that either existed). I realize that both facts (things people don't seem to know about, and things not updated in years) are for some the very definition of something that ought to be deprecated. I'm just saying that some people DO use them, and those folks will be bummed to learn that they are now declared officially deprecated and in some cases "no longer supported" (no more bug fixes, other than perhaps for security reasons).
Still, to be clear, this information I share here should have virtually no bearing on whether one *moves to* 2016. It's mostly just information about how such features will be treated in subsequent releases. And as some will know, some things have lay dormant (deprecated but never removed) for years in CFML, such as the parameterexists function, deprecated since like CF 3.1. :-)
And again, note that since nothing is "removed" in 2016, this means also that things marked as "deprecated" even as recently as CF11 have also "still not been removed". If it's not too indelicate to use a legal analogy, deprecation may be a death sentence, but circumstances may forestall that so this becomes instead "life without parole".
What do you think? Any surprises to you?
I would be curious to hear what others think. I'd ask that folks please refrain from sharing "good riddance" type messages regarding the more obvious things most are "glad to see go" (the Flash, applet, or UI components). And really, if you just want to say you're "glad to see" them or even something else here go, I'm not sure what value there is in commenting on that here. Adobe has obviously heeded your sentiment. :-)
I would be interested (as perhaps Adobe may be) to hear from any who are disappointed to hear that some feature is going away.
Finally, I'll note that there may well be mistakes in the Adobe deprecated feature document, or perhaps even in my rendering of the info (in a slightly different, and I hope helpful) way. If you see any, please let me know, and as I learn of any changes, I'll mark them here as an update.
For more content like this:
- If you may prefer direct help, rather than digging around here/elsewhere or via comments, I can help via my consulting services
- See that for more on how I can help a) over the web, safely and securely, b) usually very quickly, c) teaching you as we go, and d) with satisfaction guaranteed