[kepler-dev] [Bug 5144] renaming an actor does not persist in saved kar files

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5144

--- Comment #3 from Aaron <aschultz at nceas.ucsb.edu> 2010-12-08 17:32:42 PST ---
This was an issue because NamedObjId was not handling the MoMLChangeRequest
produced by the RenameConfigurer in ptolemy.  In revision 26448 of the kepler
trunk I have added the change to the NamedObjId.  It depends on a change to the
ptolemy trunk (revision 59945).  Because Kepler is not being built from the
ptolemy trunk I have also added that change as an override in the Kepler core
module.  ptolemy.actor.gui.RenameConfigurer should be deleted next time the
revision.txt file in the ptolemy kepler module is updated beyond revision
59945.

This change has a side effect of doubly rolling the revision on the workflow,
which is philosophically ok but perhaps annoying for the user.  I will leave
this bug open for now in the hope there is time to track down why the top level
container is having its lsid revision rolled twice on a component name change
through the ChangeRequest chain produced by the RenameConfigurer.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.