Thanks for your reply tracy, actually we did cleaning when we migrate to Flex 3. As you said may be naming conflict, but i wonder not specified in Release notes or any other bug list.
Thanks --- In [email protected], "Tracy Spratt" <tspr...@...> wrote: > > Maybe a name collision with the "result" event? > > > > Also, have you "cleaned" the Project? > > > > Tracy Spratt, > > Lariat Services, development services available > > _____ > > From: [email protected] [mailto:[email protected]] On > Behalf Of sruthi > Sent: Wednesday, April 01, 2009 4:12 PM > To: [email protected] > Subject: [flexcoders] Problem migrating from Flex 2 to Flex 3 > > > > Hi we have a component some thing like this. This code works properly with > Flex 2, but when we try to migrate to flex 3 we are getting ERROR > 1067: Implicit coercion of a value of type Array to an unrelated type > classes.ixrev.industry:ResultObject. > CellData.mxml > ------------- > <mx:Canvas xmlns:mx="http://www.adobe. <http://www.adobe.com/2006/mxml> > com/2006/mxml" width="100%" height="100%" xmlns:MyComps="common.*"> > ..... > .... > <mx:Script> > <![CDATA[ > [Bindable] > public var result:ResultObject = null; > ........ > ........ > > ]]> > </mx:Script> > <MyComps:detailListingCommodity id="detailListingId" headerIndex="0" > verticalAlign="top" result="{result}"/> > > </mx:Canvas> > > detailListingCommodity.mxml > --------------------------- > <mx:VBox xmlns:mx="http://www.adobe. <http://www.adobe.com/2006/mxml> > com/2006/mxml" width="100%" height="100%" creationPolicy="all"> > <mx:Script> > <![CDATA[ > [Bindable] > public var result:ResultObject = null; > .......... > .......... > ]]> > </mx:Script> > > .... > .... > </mx:VBox> > I dont't know why it needs implicit coercion, both are type ResultObject. > Anybody have any idea? > > Thanks > -Sruthi >
