Summary: | [Persistence] Renaming a Profile doesn't cause a save | ||||||
---|---|---|---|---|---|---|---|
Product: | [Tools] Target Management | Reporter: | Kevin Doyle <kjdoyle> | ||||
Component: | RSE | Assignee: | David Dykstal <ddykstal.eclipse> | ||||
Status: | CLOSED FIXED | QA Contact: | Martin Oberhuber <mober.at+eclipse> | ||||
Severity: | normal | ||||||
Priority: | P3 | CC: | dmcknigh | ||||
Version: | 2.0 | Keywords: | contributed | ||||
Target Milestone: | 2.0.1 | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Kevin Doyle
2007-07-19 16:35:37 EDT
Kevin -- I was just noticing this today. Can you see if you can develop a patch? Sure. I'll take a look at this. SystemProfileManager.renameSystemProfile() has a line commented out that would do a save using OLD api with FIXME. What we need to do is: RSECorePlugin.getThePersistenceManager().commitProfile(profile, 5000); RSECorePlugin.getThePersistenceManager().deleteProfile(profile.getPersistenceProvider(), oldName); This won't fix the issue completely though as the dom that is retrieved for the profile to commit still contains the old name. We need to modify RSEDOMExporter.populateRSEDOM() to set the name of the dom to the name of the profile when clean == true or profile is dirty or dom is dirty. Created attachment 77403 [details]
Renaming a profile now performs commit/delete
Legal Message: I, Kevin Doyle, declare that I developed attached code from
scratch, without referencing any 3rd party materials except material licensed
under the EPL. I am authorized by my employer, IBM Canada Ltd. to make this
contribution under the EPL.
Inspected and tested. Patch looks good. Committing. Verified fixed in I20071108. |