| Bug on adding a Stereotype on a Message? [message #1784832] |
Wed, 04 April 2018 15:10  |
 Yoann Farré
Messages: 60
Registered: November 2017 |
Member |
|
|
Hello,
I'm working to customize UML Papyrus and I tried to add a Stereotype on a Message. I completed my profile and can add the Stereotype to the wanted Message, but I obtained the following stackTrace in the console:
!ENTRY org.eclipse.ui 4 0 2018-04-04 16:51:20.739
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.ClassCastException: org.eclipse.papyrus.infra.gmfdiag.common.editpart.SilentEditpart cannot be cast to org.eclipse.gef.ConnectionEditPart
at org.eclipse.gmf.runtime.diagram.ui.editparts.ConnectionEditPart.createConnection(ConnectionEditPart.java:332)
at org.eclipse.gef.editparts.AbstractGraphicalEditPart.createOrFindConnection(AbstractGraphicalEditPart.java:339)
at org.eclipse.gef.editparts.AbstractGraphicalEditPart.refreshSourceConnections(AbstractGraphicalEditPart.java:696)
at org.eclipse.gef.editparts.AbstractGraphicalEditPart.refresh(AbstractGraphicalEditPart.java:645)
at org.eclipse.gef.editparts.AbstractConnectionEditPart.refresh(AbstractConnectionEditPart.java:226)
at org.eclipse.gmf.runtime.diagram.ui.editparts.ConnectionEditPart.access$1(ConnectionEditPart.java:1)
at org.eclipse.gmf.runtime.diagram.ui.editparts.ConnectionEditPart$5.run(ConnectionEditPart.java:1127)
at org.eclipse.papyrus.infra.emf.readonly.PapyrusROTransactionalEditingDomain.runExclusive(PapyrusROTransactionalEditingDomain.java:271)
at org.eclipse.gmf.runtime.diagram.ui.editparts.ConnectionEditPart.refresh(ConnectionEditPart.java:1124)
at org.eclipse.papyrus.infra.gmfdiag.common.editpart.ConnectionEditPart.refresh(ConnectionEditPart.java:130)
at org.eclipse.papyrus.infra.gmfdiag.common.helper.DiagramHelper.refresh(DiagramHelper.java:55)
at org.eclipse.papyrus.infra.gmfdiag.common.helper.DiagramHelper.refresh(DiagramHelper.java:90)
at org.eclipse.papyrus.infra.gmfdiag.common.helper.DiagramHelper$1.run(DiagramHelper.java:149)
at org.eclipse.papyrus.infra.ui.util.UIUtil$UIExecutorService$RunnableWrapper.run(UIUtil.java:536)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:37)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4213)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3820)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
I also tried with a Stereotype of other profiles (C/C++ or MARTE) and I obtained the same stackTrace.
To reproduce this behavior:
- Create a new sequence diagram
- Create two lifelines
- Add a message between lifelines (or Execution Specification).
- Apply a stereotype (from any profile) to the message
Is it a known bug? Am I doing something wrong?
I precise that I use the last version of Papyrus UML 3.3
Thank you for reading.
Yoann.
[Updated on: Wed, 04 April 2018 15:24] Report message to a moderator |
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.01647 seconds
Search
Help
Register
Login
Home
