As discussed part 6, a bean encapsulates a single record of data and that data doesn’t necessarily have to come from a single database table. But in this example, it does.

So after a long day of learning, it was time to chill out and party like it’s 1985.

One cool thing about going to MAX with a group is that after the first day, you can help each other avoid sessions that might not cover what you had expected. I spent the day hearing about Integration, Wall Street and Design Patterns.

Free pizza and open bars outside of every session room made for an interesting night.

Day 1 started off with egg and bacon biscuits, fruit and a whole lotta AIR.

Sunday before MAX was fun despite someone from our group missing their flight.

Ignite MAX will be this Sunday from 5 - 7 pm. Here’s the final speaker schedule.

I received notice on Thursday that my talk had been chosen as 1 of 16 presentations to be made for Ignite MAX on September 30th. Each presentation will be 5 minutes long. If you’re going to MAX, make sure to catch the show. I’ll be putting Object Oriented Coldfusion in the spotlight.

Now that we can easily retrieve and display record sets using the Gateway Object, it’s time to work with a specific record. Using a Bean to manage the properties of a single data record we can maintain strict control over a record as it is used throughout one or more applications.

One of the biggest reasons to move towards using OO concepts with Coldfusion is to build modular, extendable code libraries which are very easy to reuse throughout an application or group of applications. As a start, we’ll begin by moving queries that generally return multiple records into Gateway objects.