Inconsistent exception handling in WorkspaceCommandStackImpl and TransactionalCommandStackImpl

[pcdavid]

• 🆔 Bugzilla ID: #429315
• 📘 Project: Modeling / EMF Services / Transaction
• 🗓 Created: 2014-02-28T14:18:30Z
• ❓ Status: NEW /

[pcdavid]

Comment #0 on Fri Feb 28 2014 15:18:30 GMT+0100 (Central European Standard Time):

When a runtime exception is thrown within a Command's execute() method, the WorkspaceCommandStackImpl will propagate it to the caller while the TransactionalCommandStackImpl will swallow it. This makes it impossible to use a simpler command stack, e.g. for unit testing commands.

---

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