I've been doing some digging and it seams this has nothing to do with XIFF rather it has to do with any flex class that relies on the ResourceManager being initialized, in this case it's ArrayCollection.  The problem does not occur when you have a main mxml class, as somewhere in the class hierarchy the ResourceManager gets initialized correctly.  Unfortunately this is not the case for a straight actionscript 3 project (as in my case).

The following bug logged with Adobe is of relevance: https://bugs.adobe.com/jira/browse/SDK-12205 however  whichever way I try I cannot  get the darn ResourceManager initialized.  I'm starting to think it may be easier to have a main mxml file that references my main actionscript class.

If anybody could help out here or has any information to offer it would be greatly appreciated.

Regards

Rob

Link to same issue on Flex forums: http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?catid=585&threadid= 1340438&forumid=60

I agree, it's crazy to embed the internationalization manager into such low level utilities.  It's also crazy to do that and not provide a simple way of bootstrapping the damn thing as well.  I think Adobe see this as breaking backward compatibility, which says a lot about how they see straight actionscript projects or non mxml projects.  I see it as breaking functionality...

Having said that, since starting to use mxml, I'm starting to like it.  It really does make laying out pages much easier and the way you can use actionscript and mxml interchangeably is really quite nice.  I've still got lots of plain actionscript classes but they're generally included and laid out as part of a parent mxml file.

I admire your endeavor in branching Flex3, but it just sounds plain crazy.  Even if you really loath using mxml that much ,it is a far lesser evil than maintaining your own branch of Flex 3.