A Java developer shares common pitfalls when switching to Adobe Flex/ActionScript 3. Three key gotchas are covered: (1) Casting behaves differently in Flex — using constructor-style casting like Array() or Error() creates new objects rather than casting, so the 'as' keyword must be used instead. (2) Flex has no equals() method on Object, meaning all equality checks use reference identity, which causes issues in client/server scenarios with BlazeDS where logically equal objects may be different references. (3) Bindable setters in Flex are silently skipped when the new value equals the current value, unlike Java where setters always execute.
Sort: