Based on your syntax, it looks like you're trying to return a .NET DataSet from a WebService? Have you checked the data type of table? Perhaps it's not an Array? If WebService's makeObjectsBindable property is set to true (which it is by default), perhaps you already have an ArrayCollection (in which case the constructor for ArrayCollection does not expect another ArrayCollection... if you're trying to cast, remove the "new" keyword or use the as operator... there's no automatic coercion into ArrayCollection)? To answer your question, there's nothing different at a low level in Beta 3 (let alone Flex 3) about how it handles Arrays or ArrayCollections. However, the answer will be in what the "e.result" object graph looks like. You can either use the Flex Builder debugger or use trace() with mx.utils.ObjectUtil.toString(e.result) to get a better picture about what this object graph might have in terms of types etc... Note that while strongly-typed WebService decoding for .NET DataSets was added in Beta 2, bugs may have been fixed since. A scenario that may explain the change is that perhaps now the makeObjectsBindable property is now correctly honored for the collection or Rows in such a DataSet. ________________________________
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Clinton D. Judy Sent: Monday, December 17, 2007 9:52 AM To: [email protected] Subject: [flexcoders] Array handling from Beta 2 to Beta 3? I used to have this code working in Flex 3 Beta 2: var table:* = e.result.Tables.Table0.Rows; JFA = new ArrayCollection(table); Now that I've installed Flex 3 Beta 3, I'm getting a 1034 error, where I can't convert mx:collections:ArrayCollection to an Array. But it still appears that the Beta 2 version is running fine, as it should just be converting an ArrayCollection to an ArrayCollection. Does Beta 3 handle arrays and arraycollections much differently? Clinton Judy Web Developer Glenn O. Hawbaker, Inc.
