Thanks for the info Jeff... I'lll be looking forward to some of these
bug fixes... Meanwhile, I enabled 'autoSync' and 'autoCommit' and now
I'm getting a new Error... no code so I can't tell what's going on.
I was able to investigate the variables a little enough to know that
the managedProperty it's trying to update is called 'attributeGroups'.
See the definition of it in data-management-config and hibernate.
Note this collection loads just fine when autoSync and autoUpdate are
false.
Any ideas?
Thunder
<one-to-many property="attributeGroups" destination="AttributeGroup"
lazy="false"/>
_____________________________
<set name="attributeGroups" inverse="true" where="GROUPFK IS NULL">
<key>
<column name="MODELFK" precision="22" scale="0" not-null="true" />
</key>
<one-to-many class="AttributeGroup" />
</set>
_____________________________
TypeError: Error #1034: Type Coercion failed: cannot convert
mx.collections::[EMAIL PROTECTED] to mx.data.DataList.
at
mx.data::ConcreteDataService/http://www.adobe.com/2006/flex/mx/internal::updateArrayCollectionItems()[C:\dev\enterprise_gmc\frameworks\mx\data\ConcreteDataService.as:2995]
at
mx.data::ConcreteDataService/http://www.adobe.com/2006/flex/mx/internal::updateManagedProperty()[C:\dev\enterprise_gmc\frameworks\mx\data\ConcreteDataService.as:2065]
at
mx.data::ConcreteDataService/http://www.adobe.com/2006/flex/mx/internal::updateItem()[C:\dev\enterprise_gmc\frameworks\mx\data\ConcreteDataService.as:3225]
at
mx.data::ConcreteDataService/http://www.adobe.com/2006/flex/mx/internal::updateCache()[C:\dev\enterprise_gmc\frameworks\mx\data\ConcreteDataService.as:3144]
at
mx.data::ConcreteDataService/http://www.adobe.com/2006/flex/mx/internal::updateCacheWithId()[C:\dev\enterprise_gmc\frameworks\mx\data\ConcreteDataService.as:3050]
at
mx.data::DataList/http://www.adobe.com/2006/flex/mx/internal::processSequence()[C:\dev\enterprise_gmc\frameworks\mx\data\DataList.as:1506]
at
mx.data::Metadata/configureItem()[C:\dev\enterprise_gmc\frameworks\mx\data\Metadata.as:340]
at
mx.data::DataList/http://www.adobe.com/2006/flex/mx/internal::processSequence()[C:\dev\enterprise_gmc\frameworks\mx\data\DataList.as:1495]
at
mx.data::Metadata/configureItem()[C:\dev\enterprise_gmc\frameworks\mx\data\Metadata.as:278]
at
mx.data::DataList/http://www.adobe.com/2006/flex/mx/internal::processSequence()[C:\dev\enterprise_gmc\frameworks\mx\data\DataList.as:1495]
at
mx.data::Metadata/configureItem()[C:\dev\enterprise_gmc\frameworks\mx\data\Metadata.as:278]
at
mx.data::DataList/http://www.adobe.com/2006/flex/mx/internal::processSequence()[C:\dev\enterprise_gmc\frameworks\mx\data\DataList.as:1495]
at
mx.data::Metadata/configureItem()[C:\dev\enterprise_gmc\frameworks\mx\data\Metadata.as:278]
at
mx.data::DataList/http://www.adobe.com/2006/flex/mx/internal::processSequence()[C:\dev\enterprise_gmc\frameworks\mx\data\DataList.as:1495]
at
mx.data::Metadata/configureItem()[C:\dev\enterprise_gmc\frameworks\mx\data\Metadata.as:278]
at
mx.data::DataList/http://www.adobe.com/2006/flex/mx/internal::processSequence()[C:\dev\enterprise_gmc\frameworks\mx\data\DataList.as:1495]
at
mx.data::DataList/http://www.adobe.com/2006/flex/mx/internal::processSequenceResult()[C:\dev\enterprise_gmc\frameworks\mx\data\DataList.as:1610]
at
ConcreteDataService.as$38::DataListRequestResponder/result()[C:\dev\enterprise_gmc\frameworks\mx\data\ConcreteDataService.as:4344]
at
mx.rpc::AsyncRequest/acknowledge()[C:\dev\enterprise_gmc\frameworks\mx\rpc\AsyncRequest.as:82]
at
NetConnectionChannel.as$37::NetConnectionMessageResponder/NetConnectionChannel.as$37:NetConnectionMessageResponder::resultHandler()[C:\dev\enterprise_gmc\frameworks\mx\messaging\channels\NetConnectionChannel.as:407]
at
mx.messaging::MessageResponder/result()[C:\dev\enterprise_gmc\frameworks\mx\messaging\MessageResponder.as:202]
--- In [email protected], "Jeff Vroom" <[EMAIL PROTECTED]> wrote:
>
> We do have a bug fix release coming out pretty soon that should have the
> fixes to several FDMS bugs. It won't have the fix for this problem
> because we found it too late unfortunately.
>
>
>
> We can also produce hotfixes for any other problems though I think that
> requires going through our regular support folks.
>
>
>
> Jeff
>
