Unexpected reloaded resources on resource with fragments unloading

[pcdavid]

• 🆔 Bugzilla ID: #369260
• 📘 Project: Modeling / EMF Services / Transaction
• 🗓 Created: 2012-01-20T17:13:06Z
• ❓ Status: NEW /

[pcdavid]

Comment #0 on Fri Jan 20 2012 18:13:06 GMT+0100 (Central European Standard Time):

Build Identifier: Version: 3.6.2 Build id: M20110210-1200

Hello,

I'm having an unexpected behaviour on fragmented resource unloading.
I have a resource that is fragmented in many resources. Each fragment contains references to some of the other fragments. During unloading of the resources, warnings about resource re-loading are thrown (see the stack trace). As a result, the ResourceSet still have 2 loaded resources after unloading.
I will attach a plugin with a JUnit reproducing this issue. I'm using EMF 2.6.1.v20100914-1218.

Thanks,
Steve

Reproducible: Always

Steps to Reproduce:
1.Unload the main and fragmented resources
2.Notice that the ResourceSet still have some of these resources has loaded
3.

---

Comment #1 on Fri Jan 20 2012 18:13:45 GMT+0100 (Central European Standard Time):

Junit plugin to reproduce the issue

---

Comment #2 on Fri Jan 20 2012 18:14:20 GMT+0100 (Central European Standard Time):

---

Comment #3 on Sat May 14 2022 15:51:43 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.