Using Flash Components in multiple SWCs inside AS-only project

Question

Ok, this is a somewhat complicated issue dealing with SWCs and compilers. I've outlined steps to reproduce the problem below. I'm using the method outlined here to bring in Flash content to my project. I have 15-20 SWCs already, and it's working fine for those assets, the problem is specifically related to Flash's components (ComboBox, RadioButton etc.) If anyone has *any* advice on this, please let me know as we are completely stumped at this point!
The issue we're having involves using multiple external SWC files which contain AS3 components from Flash CS4. When two SWCs are linked to an ActionScript project (using Flash Builder 4 Beta (build 4.0.0)) there are collisions in the referenced classes which cause the most recently published SWC to knock out any duplicate classes in the other SWCs. A simple way to replicate this is as follows:
1. Create one FLA, called 'compA', drag one ComboBox, RadioButton and TextInput component onto the stage. Select all and convert to symbol, marking the symbol for export with a class name of Test1.
2. Create a second FLA, called 'compB', drag one ComboBox, Label and UIScrollbar onto the stage. Convert these to a symbol with a classname of 'Test2'.
3. Create a new ActionScript-only project in Flash Builder, called 'ComponentTest'.
4. Create a 'libs' folder in this new project. Select 'Project -> Properties -> ActionScript Build Path' and add the libs folder as a new SWC folder in the Library Path window.
5. Go back to compA.fla and right click the Test1 symbol in the library. Select 'Export SWC file...' and save it as compA.swc in the libs folder.
6. Do the same thing for compB.fla.
7. Edit ComponentTest.as and in the constructor, create an instance of Test1 and Test2, placing each on the stage.
8. Run the app, and the ComboBox will only be functional in one instance (whichever was published last.) The other ComboBox will behave like a MovieClip, cycling over the two frames in the stage asset (avatar and skin.) It will have no association to anything in the fl.* package.
Looking at the 'Referenced Libraries' in Flash Builder, compA may show it contains classes for the RadioButton and TextInput, but no ComboBox classes are referenced (sometimes it will show no classes at all, but this appears to be an unrelated bug with refreshing external libraries in Flash Builder.)
Unzipping the SWC files and examining their catalog.xml manifests shows all the necessary classes are listed (i.e. ComboBox is in both.)
Removing either SWC will cause the remaining one to work properly, so the problem appears to be in compiling the ComponentTest project which includes both.
Attempted Workarounds:
1. Create a new FLA, drag all components used in both files onto the stage and export a SWC called 'components.swc'. Add this SWC to the project's libs folder. In both compA and compB FLA files, add this SWC as an external library in the ActionScript 3.0 Publish settings. Re-export both SWCs. The theory is that the compiler will look for the required classes in the components.swc first, and thus not include them in the export, however this is not the case.
2. Same as above, deleting ComponentShim from both FLAs before exporting. The result is that no component classes are included, so all components act like MovieClips.
3. Add the Components source folder to the external library path of both FLAs, assuming the compiler will favor classpath references over compiled class references (ComponentShim). Same result.
Summary: We have been unable to find a way to use Flash Components in a project if they are referenced in more than one asset library. If we were able to import them once, and have all SWCs which need those classes use a single source, this might not be an issue, but the compiler does not appear to handle this (and we are admittedly not advanced enough to even know if this is possible.)

Answer 1

Hi!
I'm having the same problem. Any news on the matter?
Also, this looks like a very similar problem.
Best regards,
X_AmonPL.