Thanks guys - I had managed to prevent the error by instantiating the object earlier in the cycle, which let me release my build on time, but that's obviously not a solution I am happy with (ah the joys of bug-fixing someone else's code) - I will follow up your suggestions today.
On Fri, Jan 23, 2009 at 6:31 PM, Alex Harui <[email protected]> wrote: > More likely, the shared code problem as described in the modules > presentation on my blog. It can be the very same bits, but in a different > appdomain and then you'll see problems like this. > > > > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *Maciek Sakrejda > *Sent:* Friday, January 23, 2009 8:55 AM > *To:* [email protected] > *Subject:* Re: [flexcoders] very odd error > > > > This can also happen when you link against a certain class, but the > version of that class supplied at runtime has changed. E.g., > > 1. you build module foo.swf against application bar.swf with > load-externs > 2. your module uses class Baz from bar.swf > 3. you rebuild bar.swf, changing Baz slightly > 4. without rebuilding foo.swf, you run bar.swf (which loads foo.swf) > > When foo.swf attempts to use Baz, you'll get that error, because Baz > does not look like what bar.swf thinks it looks like. > > (Disclaimer: I'm not sure if this exact sequence replicates this issue-- > I'm extrapolating from my Java experience here--but I've run into this > in Flex previously under similar circumstances) > > -- > Maciek Sakrejda > Truviso, Inc. > http://www.truviso.com > > -----Original Message----- > From: nwebb <[email protected] <neilwebb%40gmail.com>> > Reply-To: [email protected] <flexcoders%40yahoogroups.com> > To: flexcoders <[email protected] <flexcoders%40yahoogroups.com>> > Subject: [flexcoders] very odd error > Date: Fri, 23 Jan 2009 12:55:50 +0000 > > Erm.... > > TypeError: Error #1034: Type Coercion failed: cannot convert > Tools.dal.dataObjects::dataoutsourcedmod...@9f82091 to > Tools.dal.dataObjects.dataOutsourcedModels > > Done all the basic checks (classname, package, constructor). There are > no two objects of the same name . Anyone else seen Flex do something > like this before? > > >
