This is a follow-on to my previous post.

As CFML developers start to learn Java and move into the realm of Spring and Hibernate, it is very important to stop and ask "What Is ColdFusion?".  ColdFusion, since CFMX, has been a J2EE application running within a J2EE server (JRun, JBoss, Tomcat, Websphere, etc.).  This is important because thinking of ColdFusion like this lets us expand our mind to what we can really do with ColdFusion.  We (CFML developers) can start to leverage J2EE services and frameworks like JPA, JNDI, JTA, and others to make ColdFusion a real player in the J2EE stack.  

Java developers are quick to dismiss ColdFusion as simply a J2EE app and miss its real potential:  It is the fastest way to get data to the web.  It is the fastest way to get data to AJAX, Flex, Silverlight, and even JavaFX (the last two via XML or web service).  I think that going forward, ColdFusion will really shine in this space and make itself be known as a the leader in moving data into RIAs.

ColdFusion also provides complex services easier than Java, .Net, Ruby, or whatever wishes they could.  Let's look at a couple of examples:  CFMAIL is, by far, the easiest way to generate email from an application.  CFPDF?  Are you kidding me?  It doesn't get any easier than this.  Don't tell the Java guys this, but it integrates with JMS easier than Java does too (look at the gateways).  These specialty services are an often used, but at times, overlooked part of ColdFusion because of their simplicity.  By the same token, they're often a source of ammo for the ColdFusion detractors.  Maybe they're just jealous.  

Simply put, at the end of the day, ColdFusion is a J2EE app that enables you to be more productive than if you were writing pure Java or CFML code, alone.  Look at it, and embrace it as such, and a whole new world will open up to you, as a CFML or Java developer.

I've been a bit busy since leaving St. Paul, so I've not had the time to collect my thoughts on cf.Objective() until today.  

My initial thoughts are that it was a better show than last year. The content was, again, top notch.  The food and hotel were great, and the people were, as always, the best part.  It was good to meet new faces and reconnect with old friends & people I only know via blog comment conversations.

There were very few sessions that I went to that disappointed me and didn't meet my expectations.  The first highlight, for me, was the coming out party for Mate (http://mate.asfusion.com) & Swiz (http://code.google.com/p/swizframework/).  I think that by this time next year, they will have matured into full fledged alternatives to Cairngorm.  They're both well on their way now.  

The second highlight was the ColdFusion 9 BOF.  It was, without a doubt, the single most rowdy session I've ever attended at a conference (my & Brian's contributions not withstanding).  As much as there were a lot of truer OO functionality pieces asked for, I couldn't help but think:  "Why not learn Java?", but that's another blog post.  The knowledge gap in the room was almost palpable, but I think the "thought leaders" of the CF Community (as someone so eloquently put it in another review) should accept the challenge and step up and help close the gap for those that want to get into hardcore CF development.  How do we do that?  I don't have a damn clue right now, I'm just throwing ideas out.

I'm going to go on record as saying that for both price and quality of content, cf.Objective() is the single best conference for ColdFusion developers, hands down.  There is no competition.  And, yes, I was a shameless shill for my buddies at 360|Flex, the Flex world's equivalent.  

That being said, you sure better know what you're doing with ColdFusion when you walk in the door.  All content can be considered "200 level" and above.  If you're a cfNoob, you'll be way lost and over your head.  Plain and simple.

On to my session.... 

I had a LOT of blank stares in my session, but I kind expected that.  I know the stuff I was doing was going to be way over a lot of people's heads.  I will be posting a comprehensive HOWTO document on setting up Spring & Hibernate with ColdFusion in the next few days.  There are a few people who really got it and even extended it to work with ColdSpring (good job, Joe).   If I confused you, just try to remember to look at ColdFusion (the server) as just another J2EE app and it will be an easier task for you.

That's about all I've got.  Feel free to comment on my session or whatever you like. 

Here is the code/slides for my cf.Objective 2008 presentation: "Enterprise MVC With ColdFusion and Java".  If you are currently sitting in my session, feel free to download the code and follow along.  If you're not in my session right now, still download the code and follow along.

Download The Code From My Google Code Site

P.S.  Don't forget to come to my BOF tonight on creating & using Open-Source Projects. 

I was having a conversation with Charlie today at lunch and we were talking about how easy it is to take an application from the browser to the desktop with AIR.  I decided that I should give you an example of how easy it is to do this.  My hotel search and call application is a good place to start.  I created a new AIR project in Flex Builder and copied the source from the Hotel Search & Call app into the project.  I copied the code from the KayakHotelSample.mxml into the main file for the AIR project.  I then changed the "mx:Application" tag to "mx:WindowedApplication" and ran the application within adl (the AIR debugger).  The app ran flawlessly the first time.  One tag is all it took to migrate a Flex app from the browser to the desktop.

Download the AIR package 

OK, so I'm really pissed off.

I'm sitting in a presentation at cf.Objective() (I will not name names) where the presenter has blatantly stolen someone else's code and passed it off as their own for the presentation. How do I know this? The person it was stolen from is sitting right next to me.

That is not cool. If you're doing a presentation, make sure you materials are you own, OR if you must use someone else's example, don't be a tool. Give credit where credit is due.