Bug #5564

dragging sdf director to the canvas causes exception

Added by Jing Tao almost 11 years ago. Updated almost 11 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


I searched sdf director and got it on the left panel. Then I tried to drag it to the canvas, but i got the exception:
com.microstar.xml.XmlException: Cannot create entity without a class name. in [external stream] at line 2 and column 22
at ptolemy.moml.MoMLParser._checkForNull(
at ptolemy.moml.MoMLParser._createEntity(
at ptolemy.moml.MoMLParser.startElement(
at com.microstar.xml.XmlParser.parseElement(
at com.microstar.xml.XmlParser.parseContent(
at com.microstar.xml.XmlParser.parseElement(
at com.microstar.xml.XmlParser.parseContent(
at com.microstar.xml.XmlParser.parseElement(
at com.microstar.xml.XmlParser.parseDocument(
at com.microstar.xml.XmlParser.doParse(
at com.microstar.xml.XmlParser.parse(
at ptolemy.moml.MoMLParser.parse(
at ptolemy.moml.MoMLParser.parse(
at ptolemy.moml.MoMLParser.parse(
at ptolemy.moml.MoMLChangeRequest._execute(
at ptolemy.kernel.util.ChangeRequest.execute(
at ptolemy.kernel.util.NamedObj.executeChangeRequests(
at ptolemy.kernel.util.NamedObj.requestChange(
at ptolemy.vergil.basic.EditorDropTargetListener.drop(
at java.awt.dnd.DropTarget.drop(
at sun.awt.dnd.SunDropTargetContextPeer.processDropMessage(
at sun.awt.X11.XDropTargetContextPeer.processDropMessage(
at sun.awt.dnd.SunDropTargetContextPeer$EventDispatcher.dispatchDropEvent(
at sun.awt.dnd.SunDropTargetContextPeer$EventDispatcher.dispatchEvent(
at sun.awt.dnd.SunDropTargetEvent.dispatch(
at java.awt.Component.dispatchEventImpl(
at java.awt.Container.dispatchEventImpl(
at java.awt.Component.dispatchEvent(
at java.awt.LightweightDispatcher.retargetMouseEvent(
at java.awt.LightweightDispatcher.processDropTargetEvent(
at java.awt.LightweightDispatcher.dispatchEvent(
at java.awt.Container.dispatchEventImpl(
at java.awt.Window.dispatchEventImpl(
at java.awt.Component.dispatchEvent(
at java.awt.EventQueue.dispatchEvent(
at java.awt.EventDispatchThread.pumpOneEventForFilters(
at java.awt.EventDispatchThread.pumpEventsForFilter(
at java.awt.EventDispatchThread.pumpEventsForHierarchy(
at java.awt.EventDispatchThread.pumpEvents(
at java.awt.EventDispatchThread.pumpEvents(

Related issues

Has duplicate Kepler - Bug #5444: Kepler can't run workflow if two instances exist at same timeIn Progress07/29/2011


#1 Updated by Jing Tao almost 11 years ago

It turns out that i have a another kepler running at my workflow run engine. When i shut it down, the error has gone.

#2 Updated by Christopher Brooks almost 11 years ago

I know this is closed, but the problem is that it appears that there
is a bug if two instances of Kepler are running.

I can't reproduce this, but I'm reopening it because the user should be able
to have two instances of Kepler running.

Jing, can you try to reproduce this?
You are running from the Kepler trunk under what platform?

#3 Updated by Derik Barseghian almost 11 years ago

I recommend closing as duplicate of: bug#5444 (which could be given a more general title)

#4 Updated by Christopher Brooks almost 11 years ago

Good point, bug#5444 includes the same stack trace.
So, I'm closing this one and marking it as a duplicate.

#5 Updated by Redmine Admin over 9 years ago

Original Bugzilla ID was 5564

Also available in: Atom PDF