ArrayStoreException: Implementation error in CompositeChangeDescription

[pcdavid]

• 🆔 Bugzilla ID: #393451
• 📘 Project: Modeling / EMF Services / Transaction
• 🗓 Created: 2012-11-02T18:32:34Z
• ❓ Status: NEW /

[pcdavid]

Comment #0 on Fri Nov 02 2012 19:32:34 GMT+0100 (Central European Standard Time):

---

Comment #1 on Fri Nov 02 2012 19:34:46 GMT+0100 (Central European Standard Time):

This patch tries to access the first modification of a list of changes using the entrySet (objectChanges.entrySet().iterator().next()).

---

Comment #2 on Fri Nov 02 2012 19:35:49 GMT+0100 (Central European Standard Time):

Fixed the collection of multiple object changes.

---

Comment #3 on Fri Nov 02 2012 19:45:11 GMT+0100 (Central European Standard Time):

The 'CompositeChangeDescription' is supposed to collect all object changes which is essentially a map between target-objects and list of applied changes (EMap<EObject, EList<FeatureChange>>).
The collection has been realized using the method EMap.addAll as EMap is a simple descendent of EList. This only adds the new changes to the list of current changes within the 'CompositeChangeDescription'.
This will fail if two sets of object changes are applied referring to the same target object since this causes two entries with the same key-objects within the list.
The map will be "screwed" up and generate an ArrayStoreException if the map will be traversed through iterating the entrySet.
The patch for the project 'org.eclipse.emf.transaction.tests' allows to alter the testscase in order to reproduce this error.
The patch for the project 'org.eclipse.emf.transaction' solves this error.

Feel free to ask for additional information.

P.S.: Sorry for this bad bug report but I'm definitely not a fan of Bugzilla.

Best regards

Daniel Kasmeroglu

---

Comment #4 on Sat May 14 2022 15:51:36 GMT+0200 (Central European Summer Time):

Eclipse EMF Transaction is moving away from this bugs.eclipse.org issue tracker to https://github.com/eclipse/emf-transaction.

If this issue is relevant to you and still present in the latest release:

* Create a new issue at https://github.com/eclipse/emf-transaction/issues/.
  * Use as title in GitHub the title of this Bugzilla ticket (may include the bug number or not, at your own convenience)
  * In the GitHub description, start with a link to this bugzilla ticket
  * Optionally add new content to the description if it can helps towards resolution
* Update bugzilla ticket
  * Add to "See also" property (up right column) the link to the newly created GitHub issue
  * Add a comment "Migrated to <link-to-newly-created-GitHub-issue>"
  * Set status as CLOSED MOVED

All issues that remain open will be automatically closed next week or so. Then the Bugzilla component for EMF Transaction will be archived and made read-only.