Eclipse Community Forums: AMW » AMW Use Case

Home » Archived » AMW » AMW Use Case - Aspect Oriented Modeling

AMW Use Case - Aspect Oriented Modeling [message #1728050]

Wed, 30 March 2016 11:30

Eclipse User

Hello

I am new to AMW and currently working on the AMW Use Case - Aspect Oriented Modeling. I tried importing the files into my eclipse workspace but when I try to open the "weave.amw" I get the following exception

Could not open the editor: An exception was thrown during initialization

On further investigation I noticed that I do not have "mm_weaving.km3" in my list of load km3 extensions.

Please how do I get this file (i.e. hoping that I am on the right track)

Thank you.

Re: AMW Use Case - Aspect Oriented Modeling [message #1728069 is a reply to message #1728050]

Wed, 30 March 2016 14:02

Eclipse User

Hi

This file is already provided in the .zip file of the AOM use case.

There is two possible options:
1- when you open the AMW wizard in order to create a new model, it is necessary to choose this file in the workspace, so it will be parsed and loaded as part of the metamodel.

2- if you want to open an existing file, it is necessary to check if the PATH indicated in the <>.prop file corresponds to the PATH of the "mm_weaving.km3" file.

Regards,

Marcos

Re: AMW Use Case - Aspect Oriented Modeling [message #1728146 is a reply to message #1728069]

Thu, 31 March 2016 07:15

Eclipse User

Thank you for pointing me in the right direction.

I can now create a new weaving model using the mm_weaving.km3 extension.

I have fixed the relative paths in the weave.amw.prop (in the AOM case study) but I can't seem to get the weave.amw to open using the editor. I get the following error

Could not open the editor: An exception was thrown during initialization

java.lang.NullPointerException
at org.eclipse.gmt.weaver.plugin.util.WeaverResourceUtil.loadKm3ExtensionStreamList(WeaverResourceUtil.java:341)
at org.eclipse.gmt.weaver.core.WeaverModelManager.getWeavingMetamodelRS(WeaverModelManager.java:313)
at org.eclipse.gmt.weaver.core.WeaverModelManager.getWeavingMetamodelRS(WeaverModelManager.java:261)
at org.eclipse.gmt.weaver.core.WeaverModelManager.getWeavingMetamodel(WeaverModelManager.java:354)
at org.eclipse.gmt.weaver.core.WeaverModelManager.initWeavingMetaModel(WeaverModelManager.java:155)
at org.eclipse.gmt.weaver.core.WeaverModelManager.<init>(WeaverModelManager.java:114)
at org.eclipse.gmt.weaver.editors.GlobalWeaverEditor.initModelManager(GlobalWeaverEditor.java:403)
at org.eclipse.gmt.weaver.editors.GlobalWeaverEditor.init(GlobalWeaverEditor.java:374)
at org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:798)
at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:647)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:465)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:289)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2863)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2768)
at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2760)
at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2711)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2707)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2691)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2682)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:651)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:610)
at org.eclipse.ui.actions.OpenFileAction.openFile(OpenFileAction.java:99)
at org.eclipse.ui.actions.OpenSystemEditorAction.run(OpenSystemEditorAction.java:99)
at org.eclipse.ui.actions.RetargetAction.run(RetargetAction.java:221)
at org.eclipse.ui.navigator.CommonNavigatorManager$3.open(CommonNavigatorManager.java:185)
at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48)
at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:845)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:843)
at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1131)
at org.eclipse.ui.navigator.CommonViewer.handleOpen(CommonViewer.java:462)
at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1235)
at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:264)
at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:258)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:298)
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:620)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
at org.eclipse.equinox.launcher.Main.run(Main.java:1408)

What can I do to fix this?

Thank you.

Re: AMW Use Case - Aspect Oriented Modeling [message #1728202 is a reply to message #1728146]

Thu, 31 March 2016 16:37

Eclipse User

Hi

it still seems a problem with the km3 extension, which cannot be loaded. Normally, it should inject the km3 file into an Ecore metamodel.

Can you copy the .prop file here ?

Marcos

Re: AMW Use Case - Aspect Oriented Modeling [message #1728319 is a reply to message #1728202]

Fri, 01 April 2016 18:22

Eclipse User

Ok, here it is.

<?xml version="1.0" encoding="UTF-8"?>
<weaver>
<weaving>
<relative-path>/AOM/weave.amw</relative-path>
<panel>DefaultWeavingPanelExtension</panel>
<wmodel>WeavingModel</wmodel>
</weaving>
<metamodels>
<plugin>
<relative-path>org.eclipse.weaver.extension.base/metamodels/mw_base_extension.km3</relative-path>
</plugin>
<local>
<relative-path>/AOM/mm_weaving.km3</relative-path>
</local>
<complete></complete>
</metamodels>
<woven id="0">
<model-relative-path>null</model-relative-path>
<metamodel-relative-path>/AOM/Communication.ecore</metamodel-relative-path>
<reference>coreModel</reference>
<title>coreModel</title>
<panel>DefaultWovenPanelExtension</panel>
<wmodelref>ModelRef</wmodelref>
</woven>
<woven id="1">
<model-relative-path>null</model-relative-path>
<metamodel-relative-path>/AOM/SimpleAdvice.ecore</metamodel-relative-path>
<reference>adviceModel</reference>
<title>adviceModel</title>
<panel>DefaultWovenPanelExtension</panel>
<wmodelref>ModelRef</wmodelref>
</woven>
</weaver>

Re: AMW Use Case - Aspect Oriented Modeling [message #1728489 is a reply to message #1728319]

Mon, 04 April 2016 16:38

Eclipse User

Hi

there is one previous post that describes a problem in the same line you had. It was related to a plugin dependency issue. The post is the following: https://www.eclipse.org/forums/index.php/t/160357/

Can you check if the problem is similar ?

Regards,

Marcos.

Re: AMW Use Case - Aspect Oriented Modeling [message #1728581 is a reply to message #1728489]

Tue, 05 April 2016 11:01

Eclipse User

Thank you Marcos, I have gone past it. I initially wanted to learn how I could merge two metamodels using AMW. I eventually got it sorted out using just ATL

Previous Topic:	Mwcore validation
Next Topic:	Is aspect-oriented modelling possible in papyrus?

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Mar 15 14:29:39 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter