BlueDragon Blog
Here you'll find tips and information about making the most of BlueDragon, which offers several compelling implementation alternatives for your CFML applications. This blog was created originally by Charlie Arehart, who was New Atlanta CTO from 2003-2006.,He has since moved on to become an independent consultant but continues to answer comments raised in existing blog entries. BlueDragon continues, and you should look to the newer BlueDragon blog, from New Atlanta president, Vince Bonfanti, for more updated information.

Why you should consider running CFML on J2EE

« H E For All CFers--not just BD :: BlueDragon Evangelism :: Charlie Arehart :: email
posted Saturday, 17 April 2004
As a CFML developer, whether you know or care about J2EE, you should understand what it means to deploy your CFML on a J2EE server and what the benefits are. I've created a few resources recently that you might want to look at, again, regardless of your experience with J2EE.

First, in the April CFDJ, I've got a a substantial article titled, "Making the Case for CFML on J2EE", available online at http://sys-con.com/story/?storyid=44481&DE=1. I explain the many benefits of deploying CFML on J2EE, whether you're being forced to consider the option, or even if you'd never think it applicable. All CFML can be improved by deploying it on J2EE, but it's still CFML.

If you, or someone you know, needs a simpler, gentler introduction, point them to the interview I did for the upcoming CFUN event, where I'll be discussing this very topic. It's available online at http://www.cfconf.org/CFUN-04/news_DeployingCFMLonJ2EE.cfm.

Finally, in a future CFDJ issue, I'll continue the talk on CFML on J2EE by showing how easy it can be, especially using BlueDragon. But the two resources above are applicable to both CF and BD users.

In the article, and in the talk I'll do at CFUN, I point to several other resources that exist on the general topic of CFML on J2EE. There have also been some new articles in the March issue of the CFDJ that I hadn't known about as I wrote the April article. See the March archives at the CFDJ site for more.


comments (3)


1. a reader left...
Saturday, 8 May 2004 11:04 am

I have a question regarding this. The company I work for host about 20+ sites all on the same box. It's not practical to run CF*/J2EE and have it's own J2EE/CF* Instance per site is it? Isn't there a limitation to how many times you can deploy a CF4J2EE/Bluedragon?

Todd


2. Charlie Arehart left...
Saturday, 8 May 2004 12:00 pm

Todd, one of the great benefits of BlueDragon's J2EE deployment option over CFMX's is that our footprint is just 10% of theirs. For instance, when you deploy on a server that requires you explode the WAR/EAR file, you see that CFMX's deployment is 110 MB. Ours is just 10MB.

So when you deploy multiple times (whether just multiple web apps on a single virtual server or multiple virtual servers), our small footprint means you can fit many more apps with BlueDragon.

Hope that answers your question.