Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 161168 - TransactionalEditingDomainImpl.FactoryImpl.unmapResourceSet doesn't work
Summary: TransactionalEditingDomainImpl.FactoryImpl.unmapResourceSet doesn't work
Status: VERIFIED FIXED
Alias: None
Product: EMF Services
Classification: Modeling
Component: Transaction (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal
Target Milestone: ---   Edit
Assignee: Christian Damus CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-16 20:50 EDT by Rick Warren CLA
Modified: 2017-02-24 15:10 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Rick Warren CLA 2006-10-16 20:50:03 EDT 
Presumably, unmapResourceSet(TransactionalEditingDomain) should remove the adapter added in mapResourceSet(TransactionalEditingDomain). Unfortunately, it doesn't seem to do anything at all. None of the adapters I see on my editing domain's resource set (and the ResourceSetDomainLink in particular) are removed.

This is a relatively big deal for anyone who needs to use a resource set outside of the context of a single editing domain, because there's no clean way to remove the ResourceSetDomainLink from the resource set without removing *all* adapters.

This bug was observed in the version of EMFT that came with the June-end Callisto release simultaneous with the Eclipse 3.2.0 release. I'm not sure what version number that corresponds to; sorry.
Comment 1 Christian Damus CLA 2006-12-07 11:48:11 EST 
Committed a fix to HEAD (version 1.1).  The unmapResourceSet() method now looks for the correct adapter type.  Also ensured that the default implementation of TransactionalEditingDomain.dispose() does this unmapping, so that after disposing an editing domain, the resource set no longer references it.
Comment 2 Nick Boldt CLA 2008-01-28 16:35:06 EST 
Move to verified as per bug 206558.