When you look at our J2EE implementation, there are many similarities to CFMX's and yet also many beneficial advantages we offer. (The previous message today discussed the more general differences and similarities betwen BlueDragon and CFMX.)
First, we (like CFMX) can offer a means to support multiple independent application instances so that if one app on the server crashes or performs poorly, it needn't affect others on the same server. Compared to CFMX for J2EE, however, our runtime is just 2MB versus over 50MB, which is especially important when running multiple independent instances.
We also offer the means to deploy both the CFML runtime and your app at once as a web application archive (WAR file), whereas with CFMX for J2EE, you deploy just the CF runtime. Some servers won't allow you to then copy/paste your CFML apps into that webapp.
And the price for our J2EE edition starts at just $2499 per CPU compared to CFMX Enterprise's $5999 for 2 CPUs.
Finally, in considering the advantages of running CFML on a J2EE server, keep in mind that you get whatever power that underlying J2EE server offers transfers to your app (session clustering, greater performance and stability, ability to run on disparate systems like mainframes, AS/400's, Mac OS/X, Netware, etc.) Running CFML on a J2EE server really changes the landscape dramatically compared to running it as an independent server.
You can learn more about BlueDragon/J2EE in our whitepaper at http://www.newatlanta.com/downloads/bluedragon/BlueDragon_CFML_on_J2EE.pdf