Judging by how often this one comes up, there seems to be much confusion and need for clarification. So …
ColdFusion MX 7 can execute compiled .cfm files, Java bytecode instead of CFML source. All editions of ColdFusion can compile CFML source for deployment, and all versions of ColdFusion can execute compiled code.
ColdFusion MX 7 also allows for the creation of deployment packages, EAR or WAR files that contain your application as well as the ColdFusion engine itself. All versions of ColdFusion can create deployment packages, however a ColdFusion Enterprise license is needed on the machine that the package is deployed to.
Clarifying Sourceless Deployment And Deployment Package Creation
10 responses to “Clarifying Sourceless Deployment And Deployment Package Creation”
-
Can the Enterprise license on the target machine be the same license that is on the machine that generated the EAR or WAR files?
-
Well, I guess if you are deploying to that same machine then sure, that would be legal. Otherwise not. ColdFusion is licensed per server (by CPU on that server), and each server needs its own license.
-
so, there is no way to compile .cfm files and deploy them to another J2EE server (Tomcat for example) without also having to purchase a CF7 Enterprise license for that J2EE server?
-
Jared, correct. The compiled .cfm files are useless with the CF engine and runtime services.
-
What about an OEM version of CFMX ? In that is there an OEM Version of CFMX that you can use (at a price per OEM of course) which allows you to bundle your application and send to a customerbase who only use cf for your app?
Ie in reading what you’ve stated, it sounds like in order to commerically use the Sourceless deployment the end customer must have Enterprise server… which in some cases will be asking someone to buy an 18 wheel truck to tow a simple caravan…
The power could go unused? -
In the past, MM has been very willing to talk about oem arrangements for distributing apps. You wind up bundling a license with your product and you get quantity discounts on the number of licenses you distribute. You generally wind up having to inventory a few cf licenses. Unfortunately, I never drove my product to a stable enough point to consider distribution (the Primary product architect decided he’d actually like to make a living).
-
There is always an option for a redistribution agreement and license. You’d need to contact MM directly on that way, probably through the partner program.
-
After the .cfm codes are compiled to bytecode, is it possible to recompile the byte code to cfm codes again?.
-
Well, bytecode can be decompiled back to Java, but it would be very hard to turn that back into CFML.
-
Er, actually I have to say that requiring an enterprise license to utilize a deployed package totally sucks (to use my most eloquent english).
–Begin caffine fueled sermon–
And here I’ve been over the last 5 years converting everyone to buy Cold Fusion and I thought we had a really workable breakthrough that made sense as to why spend six thousand dollars on an application server over the miriad of free ones out there. I am totally dismayed.
What do you think Adobe are going to do with MM anything a bit more lubricating? (sorry I guess I mean liberating?)
–End caffine fueled sermon–
Leave a Reply