Bug 163592 - [api] API needed to explicitly save profiles after model changes
Summary: [api] API needed to explicitly save profiles after model changes
Status: RESOLVED FIXED
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: 1.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 2.0   Edit
Assignee: David Dykstal CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords: api
Depends on: 142806
Blocks: 170932
  Show dependency tree
 
Reported: 2006-11-06 15:46 EST by David Dykstal CLA
Modified: 2008-08-13 13:18 EDT (History)
0 users

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 David Dykstal CLA 2006-11-06 15:46:07 EST 
A new API will be added that will explictly save the model after changes have been made. The save should be optimal in the sense that only changes made to the model should be written. The implicit saves done by the model on modification will be removed and this save operation added to all actions driven by the UI. Actions driven by code will then become responsible for saving the model at points appropriate for that code.
Comment 1 David Dykstal CLA 2006-12-21 15:48:33 EST 
Integrated first cut of RSEModelOperation - a transaction boundary wrapper
Comment 2 David Dykstal CLA 2007-05-16 16:42:49 EDT 
You can use the transaction wrapper or use ISystemProfile.commit() to explicitly save a profile.
Comment 3 Martin Oberhuber CLA 2008-08-13 13:18:43 EDT 
[target cleanup] 2.0 M7 was the original target milestone for this bug