Bug 245419 - Allow clients to set options on existing instances of unexecuted AbstractEMFOperations
Summary: Allow clients to set options on existing instances of unexecuted AbstractEMFO...
Status: RESOLVED FIXED
Alias: None
Product: EMF Services
Classification: Modeling
Component: Transaction (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P2 enhancement
Target Milestone: ---   Edit
Assignee: Christian Damus CLA
QA Contact:
URL:
Whiteboard: Client Control
Keywords: noteworthy, plan
Depends on:
Blocks:
 
Reported: 2008-08-27 13:40 EDT by Linda Damus CLA
Modified: 2017-02-24 15:11 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 Linda Damus CLA 2008-08-27 13:40:16 EDT 
Please consider adding API that would allow clients to modify the transaction options on an existing AbstractEMFOperation before it has been executed.

Currently the only way to set the transaction options is through the constructor.  However, it is common for clients to wish to execute an AbstractEMFOperation that was created by some other part of the system, and need to modify the options at the time of execution.
Comment 1 Christian Damus CLA 2008-08-27 14:13:28 EDT 
Good idea.
Comment 2 Christian Damus CLA 2008-09-21 08:23:14 EDT 
Added API to change the transaction options at any time before executing an AbstractEMFOperation:

  - void setOptions(Map<?, ?>) throws IllegalStateException
  - boolean canSetOptions()

These new operations are not final, to allow subclasses to intercept and transform incoming options, or even to disable this capability if they wish.  However, for safety reasons, only the AbstractEMFOperation implementation of the setOptions method can actually change the options.
Comment 3 Christian Damus CLA 2008-11-24 13:10:07 EST 
Restore original target after milestones were deranged.