Monday, December 31, 2012

BlazeDS Error Solved

I have been working on a fun project that requires a streaming gateway between Adobe ColdFusion and Apache Flex.  I had a vanilla installation of CF 9.0.2 (after numerous attempts to configure my current setup) and was consistently getting the error:
Unable to find the Flex adapter for destination ColdFusionGateway in the RMI registry on localhost:1099
I haven't done much Java in some time and BlazeDS installed with CF 9 is generally pretty simple, so I correctly assumed the problem was configuration related instead of going down a rabbit hole.  The problem was that this code was working on another of my machines just fine, and this is a fresh install and the config files matched.

Googling brought up the same few posts which were not related to my situation, so I wanted to post the solution here quickly in case I can save someone else 3 days of hair-pulling.

In the end I had to change the definition for the ColdFusionGateway destination in messaging-config.xml.  I had to uncomment and set the gatewayhost property to localhost as shown below:
The help text states:
If ColdFusion is running on a different host, enter that here.  Default is to expect ColdFusion and Flex to share the same web application. You must enter 'localhost' if CF and Flex are not in the same web app.
This doesn't make sense since I am calling the messaging component from within ColdFusion (BlazeDS installs with CF 9+).  This is why I couldn't figure out what setting needed flipped.  I would understand if I was getting this message in my Flex application, as in my current test environment the Flex application I am working on I am running out of Flash Builder in debug mode.  The Flex project does not live anywhere within the context of ColdFusion so this setting would make sense.

I also don't recall ever having to do this prior to ColdFusion 9.0.2.  It is also worth noting that I am on Mac OS X Mountain Lion (10.8) and also reproduced this in 9.0.2 on OS X 10.7.

Regardless, I am back up and running, and if you are reading this I hope this helps you as well.

Tuesday, July 17, 2012

Quick IntelliJ Tip - Disable Unlimited Whitespace

It drives me nuts when my code has trailing spaces at the end of a line when programming.  Why anyone would want this is beyond me.  I'm a Mac and running IntelliJ 11.1 Ultimate.  To disable this wonky feature I had to do some digging.

What you need to do is go to your IntelliJ IDEA menu and click 'Preferences'.  Select 'Editor' from the preferences panel (under IDE Settings) and in the upper right you will see a heading for 'Virtual Space'.  Uncheck 'Allow placement of caret after end of line'.  Not sure why it is named caret instead of cursor, but who cares.  I can now cmd-arrow to the front and back of the line as with Eclipse.

Wednesday, May 16, 2012

Need ColdFusion 9 with Verity? Go Get it NOW!

Rakshith, the dashingly handsome newlywed ColdFusion Product Manager just posted this on the ColdFusion Blog:
"Our contract with Verity will soon end and we will no longer be able to allow downloads that have Verity in it (CF9/CF8 installers have Verity) post 31st of May."
This means, and I can't stress it enough, that if you rely on Verity you need to go grab the 9.0.1 installer right now.  The ColdFusion Team will be releasing ColdFusion 9.0.2 on June 1 and purging all pages of 9.0.1 downloads.  9.0.2 will not contain the Verity engine, and only Solr will be an option for searching.

Saturday, March 10, 2012

Some Nifty Adobe ColdFusion 10 Language Changes

I am reviewing the Adobe ColdFusion 10 beta documentation and wanted to point out a few small things I was happy to see.  These might not be earth shattering to you, but these will affect the way I write code so I felt it was worth sharing.

Thing 1: for - in syntax for looping queries
ColdFusion 10 (codenamed Zeus) allows us to loop over queries in cfscript using for - in syntax.  This syntax was previously used for looping keys in a structure.  I had previously mentioned this in my post Dear ColdFusion Team: Please fix this stuff in Zeus as number 4.  Maybe someone read my blog, or maybe it just made that much sense ;)

The new syntax looks like this:
for ( row in myQuery ) {
  fullname = row.fName & row.lName;

How does this affect my code?
It makes life so much easier and code so much more elegant (as ColdFusion is meant to be), especially when you consider the code we write in ColdFusion 9:
for ( var x=1;x<=myQuery.recordCount;x=x+1 ) {
  fullname = myQuery.fName[x] & myQuery.lName[x];

It also feels more like the tag based alternative, which I generally think is a good thing.

Thing 2: Retrieve Application Metadata
ColdFusion 10 adds a new function called getApplicationMetadata().  This is pretty cool as when you dump out the application scope you generally only see application variables, with the exception of the application name.  The new getApplicationMetadata() function provides insight into the application settings themselves.

getApplicationMetadata() output

How does this affect my code?
I can see several uses for this, but the first one that immediately jumps to mind is that I can sync us my JavaScript timeouts with my session timeouts.  That alone is pretty big to me, since I write HTML/Ajax apps.  This helps with pingback and timeout redirection.  Some of this I can also see being really helpful for framework and 3rd party app developers.

Thing 3: onAbort Application method
Although I now have to change my ColdFusion Application.cfc presentations to stop saying 7 application events ;), I'm happy that this function has been added.  What it does is allows you to process the results when you use <cfabort> or abort;.  The new application event handler is placed in your Application.cfc file.  Here is the syntax, directly from the documentation:
<cffunction name="onAbort"
hint="Hanldes Aborted request">
<cfargument type="String"
<cfoutput> Target Page: #targetPage#</cfoutput>
<!--- do stuff --->

How will this affect my code?
To be honest, I haven't decided yet.  I imagine I will be able to start using <cfabort> for more than just debugging, but it hasn't quite solidified in my mind yet.

Thing 4: Ability to slice arrays
I don't need to go too in depth on this one.  It's something that I can do in other languages and is an important part of array handling.  Here is the syntax, right from the docs:
array = [1, 2, 3, 4, 5, 6, 7, 8];
newArray = arraySlice(array, 2, 3);//returns 2,3,4
newArray = arraySlice(array, 4);//returns 4,5,6, 7, 8
newArray = arraySlice(array, -5, 3);//returns 4,5,6

How will this affect my code?
Easy, I won't have to finagle my arrays.  We now have a language construct to slice.

Thing 5: Method chaining in CFCs
Since ColdFusion 6 we have been able to method chain to a certain degree.  This worked across multiple CFCs (following the object's composition):
employeeName = company.getEmployee().getFullname();

This should not be confused with the new method chaining within beans, which specifically affects mutator methods in our objects (if we have accessors explicitly defined of accessors="true" in our CFC definition).  Check this out:

How will this affect my code?
The jury is still out on this one for me.  I use method chaining like this in jQuery often.  I personally think it makes my code more legible.  It is certainly shorter code, but is it really better?  Not sure.

Thing 6: Structures now support colon notation
#1 on my Dear ColdFusion Team: Please fix this stuff in Zeus list, I am certainly happy to see this.  Railo already did this, as did other ECMAScript based languages such as JavaScript and ActionScript.
st = {
  name: 'Richard',
  age: 44,
  favoriteColor: 'Purple'

Again CF team, thanks for listening!

How will this affect my code?
Easy. I won't have to troubleshoot stupid errors when I move from language to language any more.  I can always use the same accepted syntax!

Other stuff
There are plenty of other language changes in ColdFusion 10.  Just because I don't use them doesn't mean they aren't great.  I encourage you to comment on some that will change the way you code.  I bet the directoryCopy() function and <cffile> improvements alone have people thinking in new ways.  Oh, and closures.

Friday, March 9, 2012

Railo, Tomcat and Apache on Amazon EC2 Ubuntu AMI

About this guide

This guide is long because I wanted to give some background info so you can not only install Railo on an Amazon Ubuntu AMI, but so that you understand why you are doing what you are doing.  If you want to see how easy this is, just skip from gray block to gray block below.  There are 13 actual commands to install Apache, Railo and Tomcat.  There are 7 lines of configuration to paste into two config files.  It doesn't get much easier.

Background on why I tried Railo in the cloud
So I've been very fortunate in my life to have been a ColdFusion developer, Ajax developer, Adobe trainer, digital media developer, Flex developer, product manager, project manager, task lead, agile trainer and Director in my short life, which has put me in the unique position to be contacted by start ups for advice on how to get going quickly using an Agile methodology.  The exciting part about this skill set is I get to help them plan their technology stack, development and deployment methods including Scrum, continuous integration, continuous builds, etc.

Now, one thing I am always sure to say is that ColdFusion should be a part of that technology stack.  See, I use ColdFusion differently than many of you.  I use it almost exclusively as a service tier.  I use Flex or HTML/Ajax for my interaction tier and ColdFusion only exists to proxy information and handle my business logic.  ColdFusion does an awesome job of this and with most start ups needing to get to minimum viable product quickly with low overhead, ColdFusion just makes sense.

Over the past 5 years I've had the luxury of working with one start up where money was no problem.  They had the best of everything from a custom data center to 5 rows of racks filled with servers and all the software and processing power we could ever need.  That has happened exactly ONE time.  Most of the start ups I have worked with are cash poor, but idea rich.  The idea that I can take ColdFusion and deploy it to the cloud with virtually no long term commitment is just plain awesome for them.  They can shut down the next day if they had to, or they could add another 10 servers in minutes.  With Amazon I helped take one company from $80k per month in data center costs down to $3k a month.  With savings like that a few Adobe ColdFusion Enterprise licenses were easy to sell.

Recently I have wanted to test Railo in the cloud as an alternative to Adobe ColdFusion for start ups, for no particular reason.  This guide is a result of that test.

Why Amazon
So I chose Amazon as my virtual host for 3 reasons:
  1. Price - can't be beat on processor time cost, and from what I remember, all incoming bandwidth is free.  This is especially important when you are working with digital media.
  2. Familiarity - I've always used Amazon.  The Amazon Management Console makes sense to me and I understand the pricing structure.
  3. Reach - They have data centers all over the place, and Amazon has always been very reliable.
 The fourth reason I could include is more for the start up themselves, but everyone is familiar with Amazon.  Its an easy sell.

Amazon EC2
I've found that Adobe ColdFusion runs great even on Amazon micro instances, depending on load and what sort of application you are running.  I usually will go with a small or large instance though for a service tier.  Amazon recently released medium instances, but I have not been able to test them yet.  For Railo I also deployed to a micro instance, mainly since this was a test.

I'm not going to go through the process of creating a new Amazon EC2 instance, but I will say that I deployed to Ubuntu 11.04 Natty Narwhal.  I am using the 64-bit version.  Your mileage may vary with other versions.

Deploying an instance takes about 5 minutes.  When done you can assign a security group or edit the default.  If this is for a public site you'll probably also want to add an elastic IP (which acts as a static IP for DNS). 

Get Ubuntu Up To Date
The first thing to do is to update Ubuntu
$ sudo apt-get update
$ sudo apt-get upgrade

Apache Installation
Next, we need to get Apache HTTP Server set up.  You technically don't need to use Apache HTTP as Apache Tomcat can serve the pages for you just fine.  I am using Apache HTTP server for familiarity and extensibility.
$ sudo apt-get install apache2

Get Railo
To install Railo I used the Tomcat/Railo installation from  You may want to have more control over it than I wanted.  I did also deploy Tomcat6 on Ubuntu the one time and downloaded Railo and deployed it manually.  It wasn't hard, but the pre-rolled installer worked just great.  The commands below are for the current version of Railo (3.3.1) at the time of this writing.  I am also using the 64-bit version.  Just go to to grab the latest correct version for your OS.
# get the railo tomcat installer
$ wget -O
# make it executable
$ sudo chmod +x
#run the installer
$ sudo ./

The installer works great on Ubuntu.  All of the defaults should be fine.  The only things I changed were the user Railo was running under (I called it 'railo', the default is 'root' so I suggest you change it) and the default Tomcat port.  The text below is a snapshot of those settings:
Installation Directory [/opt/railo]:
Tomcat Administrator Username [admin]:
Tomcat Administrator Password []: ##########
Tomcat Port [8888]: ####
Tomcat System User [root]: railo
Yes, Start Railo at Boot Time [Y/n]: 
Install Apache Connector? [Y/n]: 
Please choose an option [1] : (Apache 2.2) 
Please choose an option [2] : (64-bit)
Apache Control Script Location [/etc/init.d/apache2]: 
Apache Modules Directory [/usr/lib/apache2/modules]: 
Apache Configuration File [/etc/apache2/apache2.conf]:
Apache Logs Directory [/var/log/apache2]:

Test Railo
Well, you now have Railo installed on Tomcat. Go test Railo by going to http://localhost:8080 and you will see the welcome page.  If you want to test remotely, be sure to add 8080 as an incoming TCP rule in your Amazon security group for the Railo instance.

Connect Railo to Apache
The hardest part for me was getting Railo to work with Apache.  There are lots of guides around, but none simple enough for me.  I'll paste the steps below in one place as that's what I had problems finding.  During installation Apache was configured for the Tomcat connection.  There are a few things we need to do yet.

First, you'll need a few mods to help proxy requests from Apache HTTP to Apache Tomcat.  It is my understanding that this does the same job as the Adobe ColdFusion connector does.  Some of these might already be enabled, but it won't hurt to try adding them.  In older versions of Apache HTTP these would be in your httpd.conf file as includes.  Now, the a2enmod command will symlink the modules from mods-enabled to mods-available.
# add the necessary mods for Apache HTTP Server
$ sudo a2enmod proxy
$ sudo a2enmod proxy_http
$ sudo a2enmod proxy_scgi
$ sudo a2enmod proxy_balancer

If you are familiar with older versions of Apache HTTP, you'll understand we need to create a virtual site.  This virtual site will allow us to define a server name and link it to a host in our Tomcat configuration.  Your virtual host might be more complex than the one below, specifying directory Aliases and custom logs, but what you see below is the minimum.  In older versions of Apache you would be putting these entries into extra/httpd-vhosts.conf which are included in httpd.conf.  That would work as well, but in the current version you create a file in the /etc/apache2/sites-available directory with the name of your site.  The file below, for, is found at /etc/apache2/sites-available/
<VirtualHost *:80>
    DocumentRoot "/var/www"

Next, you'll need to enable that site (creating a symlink from sites-enabled to sites-available).  In older versions of Apache you just include the httpd-vhosts file in the main httpd.conf.  In the newer version you use a2ensite.
$ sudo a2ensite

Configuring Tomcat
The next thing we have to do is tell Tomcat about the site.  This is done in the server.xml file.  If you are following my instructions this is located at /opt/railo/tomcat/conf/server.xml.  To configure Tomcat you need to add a Host entry.  This needs to be done inside the AJP connector definition (search for '8009' in server.xml).  Make sure to put this inside the Engine definition for Catalina.  I put mine directly under the Host definition for 'localhost'.  Note that the docBase directory matches the directory I defined in my Apache site configuration.  Put yours wherever, but make sure they match.
<Host name="" appBase="webapps">
      <Context path="" docBase="/var/www" />

Finishing up
All that is left to do is restart Apache HTTP server and Apache Tomcat.
$ sudo service apache2 restart
$ sudo /opt/railo/railo_ctl restart

I had fits at this point and was getting 500 errors.  Luckily I have Mark Drew on IM and he found my issue quickly.  Permissions were wacky on my webroot (/var/www) by default.  I had to change them to 766, changed the owner to the railo user and set the group to staff.  You might have differing opinions on how to secure your own web directory.

Initially I had some issues getting Railo up and running as Tomcat was new to me (I deployed to Tomcat), but I figured it was worth learning since Adobe ColdFusion is also coming on a version of Tomcat starting in ColdFusion 10.  The cool thing about deploying to the cloud is I was able to terminate my existing instance and reload from scratch in about 15 minutes.  I did this 4 times.  I love cloud deployment!

I had help
Much thanks goes to Mark Drew for taking them time to sort out my error, letting me see his config files and helping me determine what mods I needed in Apache HTTP server, and to the following folks on Twitter who helped me at various points along the way, being very patient with my Tomcat n00b-ness.  Several of them have tutorials and installation scripts as well, so please give them the proper nod and thanks, in order of appearance:

Wednesday, March 7, 2012

Cryptic ColdFusion ORM Hibernate Error

Troubleshooting an old Adobe ColdFusion 9 application of mine today and was getting this error message:
HIBERNATE ERROR - Exception executing batch:
org.hibernate.StaleStateException: Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1
Now I also saw an error about a foreign key at one point, but who knows why. The issue was being caused during a value update. The goal is to allow the user to create a new object of type Domain inline. It's simple really, they just enter the Domain text and on the back end I make sure the Domain doesn't already exist before creating the domain and adding it to its parent entity (which they are editing at the time).

Here is the snippet of code that checks to see if the domain already exists, and creates the object if it does not:
// try to load the domain by the passed name
var domain = entityLoad("Domain", {name=arguments.value, project = o.getProject()}, true);
// if it doesn't exist, we need to create a new domain for this project
if ( NOT structKeyExists(local, 'domain') ) {
  domain = entityNew('Domain');
So what is happening above is we try to load the Domain, if it doesn't exist we create it, set the bi-di relationship to the project and then save it. The Domain is then added to the parent object. When the error is thrown no line number is given (cryptic, remember). So the most curious thing was I had another object type that was working fine. I compared them, and saw the error in my ways. Here is the offending object:
<cfcomponent persistent="true" table="sel_domain"  output="false" entityName='Domain'>
  <!---- properties ---->
  <cfproperty name="id" column="id" type="numeric" ormtype="int" fieldtype="id" generator="increment" /> 
  <cfproperty name="name" column="domain" type="string" ormtype="string"  /> 
  <cfproperty name="color" column="color" type="string" ormtype="string" default="" />
  <cfproperty name="project" cfc="com.Project" fkcolumn="projectID" fieldtype="many-to-one" />
  <cfproperty name="entities" singularname="entity" fieldtype="one-to-many" cfc="com.Entity" fkcolumn="domainid"/>  

  <cffunction name="init" returntype="Domain" access="public" output="false" hint="Constructor">
    <cfreturn this />
Can anyone guess what the issue is? If not, don't feel bad. Took me about 20 minutes to figure it out with the stack trace in front of me. I forgot to add the unsavedvalue="-1" to the id field. This can be fixed by adding that attribute, or in the case of the working object, simply removing the init() function.

The moral is that the error can be thrown when we are trying to save a disconnected object with ColdFusion ORM's entitySave() that already exists in our persistence layer. Hopefully this helps someone else make some sense of their issue!

Tuesday, February 28, 2012

Adobe Flash Roadmap

I've been reading the Adobe Flash Roadmap published last week and wanted to post a few thoughts. If you haven't read it yet, it isn't a long read so perhaps hop on over there and read it for yourself before you read my opinions. So, no doom and gloom here. Really this is the way it seems Flash has been moving for a few months now so there are no huge surprises. The first point I'd like to make is based on this text:
Looking forward, Adobe believes that Flash is particularly suited for addressing the gaming and premium video markets, and will focus its development efforts in those areas. At the same time, Adobe will make architectural and language changes to the runtimes in order to ensure that the Flash runtimes are well placed to enable the richest experiences on the web and across mobile devices for another decade.
So this is no huge surprise if you look at the effort Adobe has been putting into 3D rendering and graphics acceleration. I actually think this could be an awesome thing and would argue that the next big thing on the web will be multiplayer and social Flash based games. Not Farmville, but immersive experiences with lots of video and realism. I like the idea of architectural and language changes to speed things up. My first worry though is how the Apache Flex project will adapt to these changes. It will be imperative for the Adobe operatives in the Apache project to voice their opinions loudly, but it might become a debacle like the CFML steering committee. More on this later. The next point I'd like to make deals with:
With the growth of competition in the browser market, browser vendors are increasingly innovating and providing functionality that makes it possible to deploy rich motion graphics directly via browser technologies, a role once served primarily by Flash Player. Increasingly, rich motion graphics will be deployed directly via the browser using HTML5, CSS3, JavaScript and other modern web technologies. While the primary role of Flash Player as an engine for innovation on the web remains the same, what it is used for will change.
Well, here I take issue. I feel that HTML5 is about 2 years away from being a solution we can use for "rich motion graphics". With all of the hype around HTML5, people forget that not only does it have serious cross-browser support issues, but it also doesn't even contain many features that are considered standard and must-have in the Flash environment. Have you actually tried to deploy a video player across browsers and devices in HTML5? Phew. While I'm excited for the future of HTML5, and while everyone else is trying to find the next Javascript framework, I'll keep pushing out high quality apps for my clients using Flex and Flash today. For those of you who know me, you know that I love to tinker with video encoding, transcoding and delivery so this next one is important:
Adobe believes that Flash Player will continue to stay at the forefront of online video by innovating in key areas. These include the following:
  • Bringing Adobe's video streaming and content protection technology to more platforms in native formats
  • Supporting the needs of premium content owners
  • Closer collaboration with hardware vendors to provide high-performance quality experiences
Adobe believes that Flash has a number of fundamental and unique advantages for video:
  • Single and consistent player and codec support across browsers, platforms, and operating systems
  • Support for content protection (single DRM), which enables premium video content to be licensed for online distribution
  • Mature, full-featured, proven solution that provides a "mission critical" video platform for premium content owners, including support for ad insertion and analytics
Nothing here isn't exciting, and it all makes sense. I'm excited to see how they continue to innovate with DRM and analytics. Even more importantly, and so I don't geek out on the video stuff, is this line:
Single and consistent player and codec support across browsers, platforms, and operating systems
What I want to point out is that this closely mirrors my thoughts on why Flash and Flex are awesome. Why does Adobe embrace this with video, but they seem to forget that this is why Flex and Flash are awesome: penetration, cross-browser support, cross-OS support. I understand that Adobe is a tools company, but lets just see what Flash Next does to Flex. A few Flash Player roadmap nuggets to point out. These should be pretty exciting for game developers:
  • Support for more hardware accelerated video cards (from January 2008) in order to expand availability of hardware-accelerated content.
  • New Throttle event API (dispatches event when Flash Player throttles, pauses, or resumes content)
  • Multithreaded video decoding pipeline on PCs, which improves overall performance of video on all desktop platforms
Now, here is an "are you freaking kidding me?" moment. I wish we could've done this with Flex applications for years:
Keyboard input support in full-screen mode
The possibilities for video delivery in full-screen mode with keyboard input are immense. It closes the gap between set top based AIR apps and their sister applications on the web. I am not sure how they decided to handle security, but I'd be interested in seeing how this plays out. Here is a language enhancement that will have a far reaching effect. Sit and chew on this one for awhile and you will understand:
ActionScript workers (enables concurrent ActionScript execution on separate threads)
And now the meat:
Below are a few items being explored for the next generation of the ActionScript language and virtual machine:
  • Stringent static typing as default, with optional dynamic typing: Most stretches of most programs are expected to benefit from static typing. However, ActionScript 3 tends to lapse into dynamic typing all too easily in places where absolutely stringent static typing would be preferable. This will be corrected. Dynamic typing will still be available when needed, but it will no longer be the default for ActionScript, and it will need to be enabled explicitly.
  • Type inference: Type declarations will only be necessary in certain strategic places. Everywhere else the compiler will automatically infer suitable type declarations and treat the whole program as statically typed, even though the programmer does not have to state any types. Thus the convenience of untyped programming can be approximated quite well, while providing the performance advantages of typed programming.
  • Hardware-oriented numeric types: For example, int, uint, float, float4, byte, short, long, etc. (the exact set of types is still under discussion). Currently in ActionScript 3 integer values can overflow into floating point values. This will be changed so that numeric operations will never change the underlying representation of the numeric. We foresee this addition greatly reducing implementation complexity and improving runtime performance.
So it is no secret that I love ActionScript. I'm all about improvements and the improvements above are exciting (well except for the last bullet unless it is implemented passively as they promise). Here is the problem... we now have a language spec handled by a commercial organization, and a framework (Apache Flex) that is run by an open source group. What are the chances that these stay in line, especially given the fact that Adobe has stated ActionScript Next will not be 100% backwards compatible with AS3, which is what Flex is built on (anyone remember AS2 > AS3?). Here is my worry. As Apache starts considering their options and develops the Flex roadmap, how long until they say "We aren't going to compile to AS3 anymore, lets compile to Python or SmallTalk or ...". I'd be willing to bet you'll see a port in the near future, which means that innovation in Flex will need to take a backseat while the compiler is rewritten. I'd love to hear your thoughts!