Community
Participate
Working Groups
When you have applied multiple profiles on a UML model, and you want to unapply a subset of those profile, somtimes an IllegalStateException is raised. Steps to reproduce: 1. Create a Papyrus UML model (using class diagrams for example) 2. Apply the Marte profile 3. click on the root package (in model explorer) and go to the Properties view 4. Select a subset of applied Marte profiles 5. Try to unapply those profiles Maybe the first unapply will work, but if you try to unapply a selection of profiles more than once, you will get this error: java.lang.IllegalStateException: Cannot modify resource set without a write transaction at org.eclipse.emf.transaction.impl.TransactionChangeRecorder.assertWriting(TransactionChangeRecorder.java:348) at org.eclipse.emf.transaction.impl.TransactionChangeRecorder.appendNotification(TransactionChangeRecorder.java:302) at org.eclipse.emf.transaction.impl.TransactionChangeRecorder.processObjectNotification(TransactionChangeRecorder.java:284) at org.eclipse.emf.transaction.impl.TransactionChangeRecorder.notifyChanged(TransactionChangeRecorder.java:240) at org.eclipse.uml2.uml.internal.impl.ElementImpl.eNotify(ElementImpl.java:974) at org.eclipse.emf.common.notify.impl.NotificationImpl.dispatch(NotificationImpl.java:1033) at org.eclipse.emf.common.notify.impl.NotificationImpl.dispatch(NotificationImpl.java:1038) at org.eclipse.emf.common.notify.impl.NotifyingListImpl.remove(NotifyingListImpl.java:724) at org.eclipse.emf.common.util.AbstractEList.remove(AbstractEList.java:466) at org.eclipse.papyrus.profile.ui.compositesformodel.AppliedProfileCompositeOnModel.unapplyProfileButtonPressed(AppliedProfileCompositeOnModel.java:647) at org.eclipse.papyrus.profile.ui.compositeforview.AppliedProfileCompositeWithView.unapplyProfileButtonPressed(AppliedProfileCompositeWithView.java:57) at org.eclipse.papyrus.profile.ui.compositesformodel.AppliedProfileCompositeOnModel$5.mouseUp(AppliedProfileCompositeOnModel.java:399) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:213) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) 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:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
I get an exception however this is not similar from the one described above. Indeed when I try to remove parts of an applied profile the plug-in "org.eclipse.papyrus.diagram.common" yields the following messages : "could not find entry createCallOperationAction12CreationTool" with no stack trace enclosed with the error. This can be reproduced using the same steps as described by the reporter.
I can't reproduce these issues anymore I close the task