The AS3 convention is to use implicit get/set property methods instead.

Probably best to downcase those property names. user.email is much better than user.EMAIL, which should be a constant, and lots better than having to call user.getEMAIL() which is really against the spirit of AS3 and Flex. It’s also much faster to access these properties than to access them on the dynamic Object returned from data() since the compiler knows the type and receiver. This means code completion will work in the IDE too!

It’s really better to do initialization of defaults in the class body instead of the constructor as well since the compiler can optimize that away, but if you call methods in the constructor the compiler needs to assign a default value (null in non-primitive cases) to the properties and then set them to be the default value at runtime on each instantiation.

I’d also make those onFault and onData functions into real broadcast events that you can listen for and make all transfer objects either extend a base class with the base shared methods, or an interface, so that you can return a generic TransferRecord of any type if you need to. That’ll get rid of the (obj : *) parameter on the Bender component which means the compiler can optimize access to the functions on the transfer object and it moves all that shared code outside the CF generator and into AS code you can update without digging around in the guts of the code generator.

The way I’ve handled nice access in a project of mine was to define a const property on each generated object with a name like PROPERTIES, and then use that for figuring out what the properties are for objects inside the handler classes. That way you can move the fill() method into the Bender class and iterate over the const properties collection. Or if you’re feeling really dynamic you could just iterate over the properties in event.result and use hasOwnProperty() to check if the Transfer object has the correct method and call it that way. This saves you from generating lots and lots of code too.

Probably better that you take Transfer as an arguments, rather than initialising it in Bender.

That and I’ll have a chat to you about getMemento() function, you may have some issues with composition and lazy loading.