We haven’t really made an official announcement but we have been referring to the next release of ColdFusion as “Zeus” in all our internal and selected external communication.
So here it is, the next release of ColdFusion server would be called “Zeus” (from Greek mythology).
Some of the features of Zeus that we have announced include JRun replacement with Tomcat, new webservices engine, Solr replacing Verity, Closures and improved scheduling services.
21 Responses to “Next version of ColdFusion is codenamed “Zeus””
This is mega cool!! Luv the name Zeus.
Do we watch this spot for more info in the future??
What is the ETA for release or RCs??
Just so much to talk about.
we cant talk about the dates yet
but watch this space.. we have lots to talk about all the new cool stuffs that we are baking in.
Do we get the Lightning Bolt Back?!?!? (grin)
Oh yeah !!
JRun replacement with Tomcat; now this makes me excited… it’s about damn time
Soooo where do you go from there?
Zeus being the god of gods and all..
Can’t wait to see what Zeus can do!
This is a different release from “Link” correct?
Good question regarding Zeus vs Link codename. I see Wikipedia says: “ColdFusion version 10 was confirmed to be in-work by Adobe at Adobe MAX 2010. The internal codename for the next release of ColdFusion is “Link”, ….”
http://en.wikipedia.org/wiki/ColdFusion
We announced during cfobjective that next version of CF will be coming out sooner. So, instead of changing original vision for Link, we decided to codename this release as Zeus.
Ah thanks Hemant, I think I see the ‘link’/connection here: Centaurs pulled Zeus’s chariot, behind an army of Scorpio(n)s.. interesting story unfolding
..kinda makes me wonder what CF11′s codename will be!
Two very frustrating things about J2EE ColdFusion:
1. The neo configuration files are proprietary, deployment-specific, and must be packaged with the EAR
2. There is a problematic dependence on the administrator (or admin API) being present to change neo configurations — the application must be running to change configurations!
In the J2EE world, a leading practice is to use a single, self-contained EAR file that gets built once, then migrated through multiple environments: integration, test, production, etc. Leading J2EE applications are built to “self-configure” themselves, typically based on some bootstrap file, JNDI, or JVM property that indicates the runtime environment. The appropriate application configuration is either picked up from the container or loaded from within the application based on the environment indicator. By requiring that the deployment-specific neo files be bundled with the application, you lose this ability.
An acceptable solution would be to make CF able to load configurations (external to the EAR file itself, perhaps) dynamically at startup-time based on some bootstrap value. This would allow a single EAR file to be deployed across multiple environments.
The other problem with J2EE deployments of ColdFusion is that J2EE administrators will tend to want to manage CF applications like any other J2EE application — through the facilities provided by the app server. Having to add a JNDI datasource through the CF administrator (at runtime!) in addition to defining it in the app server seems like an unnecessary administrative step (not to mention that you LOSE any changes made through the administrator when you redeploy the EAR).
Jochem Vandieten echoes some of these concerns here:
http://jochem.vandieten.net/2010/01/15/using-ear-files-for-coldfusion-deployments/
I hope with all of my heart that these issues are being addressed with Zeus. Abandoning the unhealthy dependence on JRun seems like a very good step in the right direction.
For the love of Zeus!!!
I hope adobe do a mayor update or even upgrade to CF Report Builder…!!!
Please…!!!!
hello,
Since using CF7,8 & 9 and becoming well acquainted with JVM changes via editing JVM.CONFIG (C:\ColdFusion9\runtime\bin), will I expect similar “growing pains” with learning to apply changes to server.xml (C:\Program Files\Apache Software Foundation\Tomcat 7.0\conf) with CF10?
Thanks in advance, Carl.
I am VERY curious about the extJS integration. Will extJS be updated or will it be replaced with JQuery, etc?
I almost think they should leave javascript frameworks out of it. If they do tie to a framework they should solve the issue of keeping current with it.
rumours have been for a while that ‘key’ people are brainwashing the ExtJs out of ColdFusion. (or at least trying to)
Personally the whole admin would be better off it was built in ExtJS, the grids are second to nothing, and the calendar and scheduler functionality is also second to none, and the MVC stuff in version 4.0 is mind-blowingly good.
Gr8 to hear this bit of info…………..Really excited for the official release………..Plus a help document mentioning the major enhancements will be of great help going forward………
Eagerly waiting ……..
Regards,
Abhijit
While changing the Java engine and adding a lightning bolt sounds exciting I’m not a big fan of CF 9 and think you should stop and take stock of all the problems it is causing for many, many of us who have been developing CF applications for years. We have a distributed product – an application with over 7,000 templates just to give you an idea of the size. It allows us to provide income and benefits to over 30 employees as it is used by over 100 companies, many of which are atop the Fortune 500 list. This application is responsible for CF licensing fees for over 120 servers and I can’t tell you what a bad taste it has left for may IT departments. Solr that doesn’t work, log files that loop to themselves, extremely slow CFHTTP (and I’m just getting started). The number of hours on the phone with Adobe support by our support department, the charge that Adobe requires for support, and the fees we are having to give back to our customers because of server outage has become absolutely unacceptable. Zeus… really???? Stop with that development and get CF 9 stable first. If you don’t there will be even more companies migrating from CF to other middleware to provide incomes for themselves to insure they can provide for their families – it’s that simple
Nicely said!
Hopefully Windows 7 and SQL Server 2008 R2 installation is less rocky. Proper IIS7 installation too.
Not game to apply any hotfixes for fear of breaking the server again and losing days of productivity (hotfix 2 caused more problems than it solved).
Missed the cut for the Zeus alpha by the looks of it… usually get into it sooper early but no dice
Love Mr cfspreadsheet