TransactionalAdapterFactoryContentProvider could expose domain for subclasses

[pcdavid]

• 🆔 Bugzilla ID: #308171
• 📘 Project: Modeling / EMF Services / Transaction
• 🗓 Created: 2010-04-06T09:57:06Z
• ❓ Status: NEW /

[pcdavid]

Comment #0 on Tue Apr 06 2010 11:57:06 GMT+0200 (Central European Summer Time):

Build Identifier: 20100218-1602, plugin org.eclipse.emf.transaction.ui_1.3.1.v20090819-1457

Class TransactionalAdapterFactoryContentProvider does not provide any access to field domain.

Subclasses than have to keep their own copy of this object. I think that this arrangement is not necessary. TransactionalAdapterFactoryContentProvider could expose the TransactionalEditingDomain via a new protected method getEditingDomain().

The same applies to TransactionalAdapterFactoryLabelProvider.

Reproducible: Always

---

Comment #1 on Tue Apr 06 2010 17:47:17 GMT+0200 (Central European Summer Time):

Can you provide a quick patch for the access you require?

---

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