Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » Papyrus » Bug on Sequence Diagram?(Relative to state invariant and message)
Bug on Sequence Diagram? [message #1796722] Thu, 18 October 2018 07:17 Go to next message
Yoann Farre is currently offline Yoann FarreFriend
Messages: 116
Registered: November 2017
Senior Member
Hello,

I maybe found a new bug on the sequence diagram.

How to reproduce the behavior:
- Create a new UML Papyrus project
- Create a new sequence diagram
- Add two lifelines on the diagram
- Add a state invariant on each lifeline
- Then add a message between the lifeline (Async but works with other kinds of message too)
- After creation , press Ctrl + Z

Result:

In the model:
- The state Invariant are removed at the same time that the message
- The MessageOccurenceSpecification items are still in the model

In the diagram:
- The state invariant items are visible but tagged as imported
- They can be delete from the diagram only with "Delete from diagram"

If we let the state invariants in the diagram and then close/open again the model, the state invariants seem to have the lifeline as underlying EObject...

I use the 4.2.2018100202 Papyrus version.

Can someone reproduce this bug?

Yoann.

Re: Bug on Sequence Diagram? [message #1797145 is a reply to message #1796722] Fri, 26 October 2018 09:06 Go to previous messageGo to next message
Yoann Farre is currently offline Yoann FarreFriend
Messages: 116
Registered: November 2017
Senior Member
Hello,

I have just updated my papyrus version to the last nightly build (Papyrus 4.2.0.201810260257) and I have detected another bug regarding lifelines and State Invariant.

If the lifeline has a stereotype, I can't create a state invariant on it (works well if the lifeline has no stereotype).

To reproduce the bug:
- Create a new UML Papyrus project
- Create a new sequence diagram
- Add a lifeline and add a stereotype to this lifeline (any stereotype)
- Try to add a state invariant on the lifeline

Error stack trace:

java.lang.IllegalArgumentException: Anchor anchor is not a valid BaseSlidableAnchor
at org.eclipse.papyrus.infra.gmfdiag.common.helper.IdentityAnchorHelper.getYPercentage(IdentityAnchorHelper.java:95)
at org.eclipse.papyrus.uml.diagram.sequence.referencialgrilling.DisplayEvent.getMessageEvent(DisplayEvent.java:339)
at org.eclipse.papyrus.uml.diagram.sequence.referencialgrilling.DisplayEvent.getMessageEvent(DisplayEvent.java:95)
at org.eclipse.papyrus.uml.diagram.sequence.referencialgrilling.LifelineCreationEditPolicy.getCreateElementAndViewCommand(LifelineCreationEditPolicy.java:85)
at org.eclipse.gmf.runtime.diagram.ui.editpolicies.CreationEditPolicy.getCommand(CreationEditPolicy.java:87)
at org.eclipse.papyrus.infra.gmfdiag.dnd.policy.CustomizableDropEditPolicy.getCommand(CustomizableDropEditPolicy.java:121)
at org.eclipse.gef.editparts.AbstractEditPart.getCommand(AbstractEditPart.java:502)
at org.eclipse.gmf.runtime.diagram.ui.editparts.GraphicalEditPart.access$1(GraphicalEditPart.java:1)
at org.eclipse.gmf.runtime.diagram.ui.editparts.GraphicalEditPart$1.run(GraphicalEditPart.java:482)
at org.eclipse.papyrus.infra.emf.readonly.PapyrusROTransactionalEditingDomain.runExclusive(PapyrusROTransactionalEditingDomain.java:273)
at org.eclipse.gmf.runtime.diagram.ui.editparts.GraphicalEditPart.getCommand(GraphicalEditPart.java:477)
at org.eclipse.gmf.runtime.diagram.ui.editpolicies.CreationEditPolicy.getUnspecifiedTypeCreateCommand(CreationEditPolicy.java:395)
at org.eclipse.gmf.runtime.diagram.ui.editpolicies.CreationEditPolicy.getCommand(CreationEditPolicy.java:85)
at org.eclipse.papyrus.infra.gmfdiag.dnd.policy.CustomizableDropEditPolicy.getCommand(CustomizableDropEditPolicy.java:121)
at org.eclipse.gef.editparts.AbstractEditPart.getCommand(AbstractEditPart.java:502)
at org.eclipse.gmf.runtime.diagram.ui.editparts.GraphicalEditPart.access$1(GraphicalEditPart.java:1)
at org.eclipse.gmf.runtime.diagram.ui.editparts.GraphicalEditPart$1.run(GraphicalEditPart.java:482)
at org.eclipse.papyrus.infra.emf.readonly.PapyrusROTransactionalEditingDomain.runExclusive(PapyrusROTransactionalEditingDomain.java:273)
at org.eclipse.gmf.runtime.diagram.ui.editparts.GraphicalEditPart.getCommand(GraphicalEditPart.java:477)
at org.eclipse.gef.tools.TargetingTool.getCommand(TargetingTool.java:123)
at org.eclipse.gmf.runtime.diagram.ui.tools.CreationTool.getCommand(CreationTool.java:277)
at org.eclipse.gef.tools.CreationTool.handleMove(CreationTool.java:253)
at org.eclipse.gmf.runtime.diagram.ui.tools.CreationTool.handleMove(CreationTool.java:258)
at org.eclipse.gef.tools.AbstractTool.mouseMove(AbstractTool.java:1182)
at org.eclipse.gef.EditDomain.mouseMove(EditDomain.java:287)
at org.eclipse.gef.ui.parts.DomainEventDispatcher.dispatchMouseMoved(DomainEventDispatcher.java:365)
at org.eclipse.draw2d.LightweightSystem$EventHandler.mouseMove(LightweightSystem.java:543)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:216)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4145)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1055)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3958)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3561)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:628)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:563)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:151)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:155)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:199)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:391)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:246)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595)
at org.eclipse.equinox.launcher.Main.run(Main.java:1501)
at org.eclipse.equinox.launcher.Main.main(Main.java:1474)

Yoann.

Re: Bug on Sequence Diagram? [message #1799356 is a reply to message #1797145] Wed, 05 December 2018 14:32 Go to previous messageGo to next message
Yoann Farre is currently offline Yoann FarreFriend
Messages: 116
Registered: November 2017
Senior Member
Hi,

I reported a bug on Bugzilla. In fact, this bug is true for any element created on a lifeline with stereotype (state invariant, message, action execution specification...). It's quite critical when a model uses a lot of stereotypes.

Bug : 542434
Re: Bug on Sequence Diagram? [message #1799359 is a reply to message #1799356] Wed, 05 December 2018 15:13 Go to previous messageGo to next message
Morteza Sherafati is currently offline Morteza SherafatiFriend
Messages: 2
Registered: September 2018
Junior Member
I tried to reproduce your bug but my StateInvariants are still in the place and not changed.
Re: Bug on Sequence Diagram? [message #1799462 is a reply to message #1799359] Fri, 07 December 2018 08:25 Go to previous messageGo to next message
Yoann Farre is currently offline Yoann FarreFriend
Messages: 116
Registered: November 2017
Senior Member
Hi,

About the first bug, yes the StateInvariants are still visible on the diagram but not in the model explorer (the view still exists but not the UML element). And if I try to close/open the model and the sequence diagram, the stateInvariant is displayed as an element on the lifeline but don't refer to a stateInvariant in the model.

For the second bug, I can't create an element (including a stateinvariant) when a stereotype is applied.

Regards.

Yoann.
Re: Bug on Sequence Diagram? [message #1799833 is a reply to message #1799462] Fri, 14 December 2018 13:04 Go to previous messageGo to next message
Yupanqui Munoz is currently offline Yupanqui MunozFriend
Messages: 8
Registered: December 2014
Location: Paris Saclay, France
Junior Member
Hi Yoann,

The first bug is really a bug. I will report it on bugzilla. Thanks!

Best regards,

Yupanqui
Re: Bug on Sequence Diagram? [message #1799834 is a reply to message #1799833] Fri, 14 December 2018 13:11 Go to previous messageGo to next message
Yupanqui Munoz is currently offline Yupanqui MunozFriend
Messages: 8
Registered: December 2014
Location: Paris Saclay, France
Junior Member
Bug: 542802
Re: Bug on Sequence Diagram? [message #1799893 is a reply to message #1799834] Mon, 17 December 2018 07:20 Go to previous message
Yoann Farre is currently offline Yoann FarreFriend
Messages: 116
Registered: November 2017
Senior Member
Hi Yupanqui,

Thank you too !

Best regards.

Yoann.
Previous Topic:[SysML] Model validation error
Next Topic:Rhapsody import module
Goto Forum:
  


Current Time: Mon Dec 16 01:51:57 GMT 2019

Powered by FUDForum. Page generated in 0.02398 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top