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

bugzilla-daemon at ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Sat Dec 4 23:54:51 PST 2010


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

David Welker <david.v.welker at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|david.v.welker at gmail.com    |aschultz at nceas.ucsb.edu

--- Comment #2 from David Welker <david.v.welker at gmail.com> 2010-12-04 23:54:50 PST ---
I have made major progress in diagnosing this bug. Basically, the issue is not
whether you change the "title" (which is a property unique to Display actors)
but whether you change any property on the actor besides the name.

If you change a property besides the name, then a new LSID is generated and
used for the entity. This causes the name you give to the actor to persist. In
contrast, if you the only thing you change on the actor itself is the name,
then the LSID for the Display actor (or whatever other actor you are using) is
used instead of a new one being generated. For this reason, the name of the
Display actor rather than your changes show up in the KAR file.

The way to fix this bug is as follows. A change to the name of the actor needs
to be treated just like a change to the value of another property when
"Configure Actor" is selected when you right-click on an actor.

I have started to look through the LSID code to fix this bug, but I have
determined it is complicated enough that Aaron probably should be the one to
fix this so that any changes I make do not cause unexpected side-effects
elsewhere. However, if Aaron is not available, I can fix this bug. For now, I
am assigning the bug to Aaron on the assumption that he is available for this
task.

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


More information about the Kepler-dev mailing list