Project

General

Profile

Bug #5051

Semantically annotate during Save Archive a workflow with remote data set Error

Added by Derik Barseghian about 9 years ago. Updated about 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
general
Target version:
Start date:
06/16/2010
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5051

Description

If you search for a remote data set, drag it out to canvas, then Save Archive, and then Semantically Annotate the workflow, you'll get a NameDuplicationException and the window will dispose, and the kar is failed to be saved properly (and thus a new window with the saved workflow does not open (as is usually the case)).

I'm seeing this in RC5, 2.0 branch, and trunk.

Replicate:
Start Kepler, change to Data tab
Search Data for: aphid
drag out the 2nd dataset (Sedgwick Reserve Aphid Population Growth Rate Experiment)
File => Save Archive
Name workflow myWorkflow
Click yes to semantically annotate
Select a category, like Local Input, and move it to Selected Categories
Click ok, Click Save, and the window will dispose with the NameDuplicationError


Related issues

Blocked by Kepler - Bug #4943: RC5 Installer Tracking BugResolved04/19/2010

History

#1 Updated by Derik Barseghian about 9 years ago

This is the trace. Note also warning at top about cloning:

trying to clone myworkflow but you can't clone this object for some reason: Problem cloning 'output'
ptolemy.kernel.util.NameDuplicationException: Attempt to insert object named "semanticType" into a container that already contains an object with that name.
at ptolemy.kernel.util.NamedList.append(NamedList.java:133)
at ptolemy.kernel.util.NamedObj._addAttribute(NamedObj.java:2165)
at ptolemy.kernel.util.Attribute.setContainer(Attribute.java:398)
at ptolemy.data.expr.Variable.setContainer(Variable.java:819)
at ptolemy.kernel.util.Attribute.<init>(Attribute.java:109)
at ptolemy.kernel.util.Attribute.<init>(Attribute.java:86)
at ptolemy.kernel.util.AbstractSettableAttribute.<init>(AbstractSettableAttribute.java:88)
at ptolemy.data.expr.Variable.<init>(Variable.java:255)
at ptolemy.data.expr.Parameter.<init>(Parameter.java:125)
at ptolemy.data.expr.StringParameter.<init>(StringParameter.java:76)
at org.kepler.sms.SemanticType.<init>(SemanticType.java:86)
at org.kepler.objectmanager.ActorMetadata.getActorAsNamedObj(ActorMetadata.java:852)
at org.kepler.kar.handlers.ActorMetadataKAREntryHandler.open(ActorMetadataKAREntryHandler.java:226)
at org.kepler.kar.KARFile.open(KARFile.java:925)
at org.kepler.kar.KARFile.openKARContents(KARFile.java:695)
at org.kepler.gui.kar.ExportArchiveAction.actionPerformed(ExportArchiveAction.java:418)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1882)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2202)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
at javax.swing.AbstractButton.doClick(AbstractButton.java:334)
at apple.laf.ScreenMenuItem.actionPerformed(ScreenMenuItem.java:95)
at java.awt.MenuItem.processActionEvent(MenuItem.java:597)
at java.awt.MenuItem.processEvent(MenuItem.java:556)
at java.awt.MenuComponent.dispatchEventImpl(MenuComponent.java:298)
at java.awt.MenuComponent.dispatchEvent(MenuComponent.java:286)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:466)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:176)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)

#2 Updated by Sean Riddle about 9 years ago

I'm pretty sure this is fixed. Will test briefly against trunk and release and close if so.

#3 Updated by Sean Riddle about 9 years ago

Okay, it is indeed fixed in the trunk and in the release branch. I tested the release, which did not work, but having the fix in the release branch should cause it to get pulled down to the release copy at some point using the PatchChecker mechanism. I am not sure how to tell if the PatchChecker has noticed updates, or if it has successfully integrated them.

#4 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 5051

Also available in: Atom PDF