flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Mclean (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FLEX-33005) HierarchicalCollectionView does not update indexes for internal arrays when object uid changes
Date Wed, 12 Mar 2014 21:14:44 GMT

     [ https://issues.apache.org/jira/browse/FLEX-33005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Justin Mclean updated FLEX-33005:

    Labels: easyfix easytest  (was: )

> HierarchicalCollectionView does not update indexes for internal arrays when object uid
> ----------------------------------------------------------------------------------------------
>                 Key: FLEX-33005
>                 URL: https://issues.apache.org/jira/browse/FLEX-33005
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Advanced Data Grid
>    Affects Versions: Adobe Flex SDK Previous
>         Environment: Affected OS(s): All OS Platforms
> Language Found: English
>            Reporter: Adobe JIRA
>              Labels: easyfix, easytest
>         Attachments: FLEX-33005.patch
> Steps to reproduce:
> 1. Configure Data Services with Parent/Child bidirectional association between two Managed
> 2. Set up an Advanced Data Grid to display the data using HierarchicalData object as
data source.
> 3. Create Parent, Commit
> 4. Create a Child for the parent, with one more Child below
> 5. Add the first Child to the Parent children array
> 6. Expand the first Child in the Advanced Data Grid, to display the second Child, Commit
>  Actual Results:
> The first Child node will close during ConcreteDataService.internalUpdateCache.  Now
the control doesn't know how many items are in the list.  Drag and Drop operations that hover
over the empty rows close to the bottom of the list will crash the Advanced Data Grid control.
 The internal arrays indexed by UID are now stale, and leak memory.
>  Expected Results:
> No crash, leak or auto-closing tree nodes.
> Workaround (if any):
> None tested.  Maybe one could avoid adding the records to the managed association collections
on the client side at all, to prevent Advanced Data Grid from having knowledge about the temporary
UIDs, and just refresh fill every time an inserted record happens?

This message was sent by Atlassian JIRA

View raw message