Custom Application Class Embed problem aka AMBIGUOUS

Question

package  
com.drdynscript.examples{
import mx.controls.Image; 
import mx.core.Application; 
import mx.core.BitmapAsset; 
import nl.demonsters.debugger.MonsterDebugger; 
public class FlexTestApp4 extends Application{
//EXTERNAL IMAGE
Embed(source="./assets/logo.jpg")][
Bindable] private var logoClass:Class; 
//UI COMPONENTS
Bindable] public var imgLogo:Image;[
Bindable] public var imgLogo2:Image; 
public function FlexTestApp4(){
super(); 
//INITIALIZE
init();
private function init():void
//MONSERT DEBUGGER
MonsterDebugger.
trace(this, "INIT");}
public function createImage():void{
var imgObj:BitmapAsset = new logoClass() as BitmapAsset;imgObj.bitmapData.noise(4);
imgLogo2.source = imgObj;
MY MXML
<?xml version="1.0" encoding="utf-8"?><drdynscript:FlexTestApp4  xmlns:mx="
http://www.adobe.com/2006/mxml" layout="absolute" xmlns:drdynscript="
com.drdynscript.examples.*">
 <mx:Style>
 Application
 backgroundImage: Embed(source="./assets/District9.png")
</mx:Style>  
<mx:Image x="10" y="10" width="493" height="500" id="imgLogo" source="{logoClass}"/> //DOESNT WORK AMBIGUOUS
 <mx:Image id="imgLogo1" source="@Embed(source='./assets/logo.jpg')"/>
 <mx:Image id="imgLogo2" creationComplete="createImage()"/></drdynscript:FlexTestApp4>

Answer 1

I stumbled over this problem today, too.
First, let me say that that problem did not exist with previous versions of the JWSDP. Now with 1.2 I noticed that wscompile generates class files with the same names as the custom classes that you wish to send over the net. Either this design is complete rubbish or indeed intentional, but the users are left alone, at least till the new tutorial is released.
The solution that seems to work for me is to simply replace the classes generated by wscompile with the original ones.
However I do not know if this will cause any problems or is the right way to handle the situation. Hopefully anybody of the responsible engineers at Sun will comment on this.
Regards,
Ingo