<Alex impression> Sounds like a shared code module problem, check my blog for more details.
http://blogs.adobe.com/aharui/ </Alex impression> Personally, yeah your analysis sounds about right. How are you loading the module in? Into a child app domain? Gk. Gregor Kiddie Senior Developer INPS Tel: 01382 564343 Registered address: The Bread Factory, 1a Broughton Street, London SW8 3QJ Registered Number: 1788577 Registered in the UK Visit our Internet Web site at www.inps.co.uk <blocked::http://www.inps.co.uk/> The information in this internet email is confidential and is intended solely for the addressee. Access, copying or re-use of information in it by anyone else is not authorised. Any views or opinions presented are solely those of the author and do not necessarily represent those of INPS or any of its affiliates. If you are not the intended recipient please contact [EMAIL PROTECTED] ________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of hr1ny Sent: 06 October 2008 22:29 To: flexcoders@yahoogroups.com Subject: [flexcoders] Type Coercion error in a Popup module Hi, I have a module that runs inside a popup window. It runs fine the 1st time I run it, but after it runs successfully (and I unload the module), after I create and use a 2nd popup using the same module, it fails with this error: TypeError: Error #1034: Type Coercion failed: cannot convert com.adobe.createmeeting.events::[EMAIL PROTECTED] to com.adobe.createmeeting.events.CreateMeetingEvent. The error occurs while executing a piece of typical Cairngorm-style code: override public function doExecute(event:CairngormEvent):void { var myEvent:CreateMeetingEvent = CreateMeetingEvent(event); If I define the class CreateMeetingEvent and instantiate it in the parent application, then this error does not occur, but I do not want to define it in the parent application, since it does not belong there. My guess is that this has to do with the issue of ApplicationDomains and class loading. Somehow, when I create the 2nd popup with the same module, it is looking for the class definition that belonged to the now-defunct class module. Can anyone suggest what is the best way to fix this? Thanks, Henry
