Home » Modeling » OCL » Problem when opening Ecore file with OCLInEcore using Juno
| Problem when opening Ecore file with OCLInEcore using Juno [message #1069007] |
Sun, 14 July 2013 20:44  |
Eclipse User |
|
|
|
Hi,
I wanted to open the Ecore file of the BPEL metamodel using the OCLInEcore editor, but i didn't succeed. When i try to open it with the Sample Reflective Ecore model editor it shows the following erros:
java.io.IOException: Unable to resolve plug-in "platform:/plugin/org.eclipse.wst.wsdl/model/WSDL.ecore".
at org.eclipse.core.internal.runtime.PlatformURLPluginConnection.parse(PlatformURLPluginConnection.java:64)
at org.eclipse.core.internal.runtime.PlatformURLPluginConnection.resolve(PlatformURLPluginConnection.java:75)
at org.eclipse.core.internal.boot.PlatformURLHandler.openConnection(PlatformURLHandler.java:67)
at org.eclipse.osgi.framework.internal.protocol.URLStreamHandlerProxy.openConnection(URLStreamHandlerProxy.java:112)
at java.net.URL.openConnection(Unknown Source)
at org.eclipse.emf.ecore.resource.impl.URIHandlerImpl.createInputStream(URIHandlerImpl.java:171)
at org.eclipse.emf.ecore.resource.impl.ExtensibleURIConverterImpl.createInputStream(ExtensibleURIConverterImpl.java:354)
at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1256)
at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoad(ResourceSetImpl.java:259)
at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoadHelper(ResourceSetImpl.java:274)
at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getResource(ResourceSetImpl.java:406)
at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getEObject(ResourceSetImpl.java:220)
at org.eclipse.emf.ecore.util.EcoreUtil.resolve(EcoreUtil.java:197)
at org.eclipse.emf.ecore.util.EcoreUtil.resolve(EcoreUtil.java:257)
at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eResolveProxy(BasicEObjectImpl.java:1473)
at org.eclipse.emf.ecore.impl.EGenericTypeImpl.getEClassifier(EGenericTypeImpl.java:566)
at org.eclipse.emf.ecore.provider.EGenericTypeItemProvider.getText(EGenericTypeItemProvider.java:493)
at org.eclipse.emf.ecore.provider.EClassItemProvider.getText(EClassItemProvider.java:331)
at org.eclipse.emf.edit.ui.provider.AdapterFactoryLabelProvider.getText(AdapterFactoryLabelProvider.java:374)
at org.eclipse.jface.viewers.WrappedViewerLabelProvider.getText(WrappedViewerLabelProvider.java:108)
at org.eclipse.jface.viewers.WrappedViewerLabelProvider.update(WrappedViewerLabelProvider.java:164)
at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:152)
at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:953)
at org.eclipse.jface.viewers.AbstractTreeViewer$UpdateItemSafeRunnable.run(AbstractTreeViewer.java:113)
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.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:1033)
at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:485)
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.updateItem(StructuredViewer.java:2167)
at org.eclipse.jface.viewers.AbstractTreeViewer.createTreeItem(AbstractTreeViewer.java:848)
at org.eclipse.jface.viewers.AbstractTreeViewer$1.run(AbstractTreeViewer.java:823)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:797)
at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:644)
at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:768)
at org.eclipse.jface.viewers.AbstractTreeViewer.handleTreeExpand(AbstractTreeViewer.java:1500)
at org.eclipse.jface.viewers.TreeViewer.handleTreeExpand(TreeViewer.java:952)
at org.eclipse.jface.viewers.AbstractTreeViewer$4.treeExpanded(AbstractTreeViewer.java:1511)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:132)
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.Widget.sendEvent(Widget.java:1077)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1062)
at org.eclipse.swt.widgets.Tree.wmNotifyChild(Tree.java:7565)
at org.eclipse.swt.widgets.Control.wmNotify(Control.java:5534)
at org.eclipse.swt.widgets.Composite.wmNotify(Composite.java:1896)
at org.eclipse.swt.widgets.Control.WM_NOTIFY(Control.java:5086)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:4584)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4976)
at org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:2440)
at org.eclipse.swt.widgets.Tree.callWindowProc(Tree.java:1534)
at org.eclipse.swt.widgets.Tree.WM_LBUTTONDOWN(Tree.java:6435)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:4564)
at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:5958)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4976)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2546)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3756)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
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:353)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
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:629)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
i put the WDSDL, XSD, partnerlinktype, and the messageproperties Ecore files together with the bpel.ecore file in the same directory.
Any help please.
|
|
|
| Re: Problem when opening Ecore file with OCLInEcore using Juno [message #1069036 is a reply to message #1069007] |
Sun, 14 July 2013 22:30  |
| Eclipse User |
|
|
|
Hi,
I found a solution to the problem, i change the URI in the imports. for Example,
import wsdl_0 : '/plugin/org.eclipse.wst.wsdl/model/WSDL.ecore#/';
becomes:
import wsdl_0 : 'WSDL.ecore#/';
But, i have another problem:
I created a dynamic instance from my bpel.ecore file with some activities. I tried to set for example the receive activity with some attributes like, operation, portType, which are normally in the WSDL file, but without success. When i try to validate the XMI file obviously it doesn't work, and displays that these features must be set.
How to do this?
Thanks in advance.
|
|
|
| Re: Problem when opening Ecore file with OCLInEcore using Juno [message #1069155 is a reply to message #1069036] |
Mon, 15 July 2013 05:28 |
| Eclipse User |
|
|
|
Hi
If you want to use an installed version you should import the package
e.g. 'http:/...WSDL...'
If you want to use a development/installed version you should import the
packge e.g. 'platform:/plugin/org.eclipse.wst.wsdl/model/WSDL.ecore#/'
The #/ navigates from the model root to the package. You can import the
model root, in which case you then need to specify the package name in
your navigation expressions.
------
I've no idea what your second problem is. It seems to me that you should
just learn to define Ecore operations and properties, so I'm obviously
not understnading your problem.
Regards
Ed Willink
On 15/07/2013 03:30, zernadji tarek wrote:
> Hi, I found a solution to the problem, i change the URI in the
> imports. for Example, import wsdl_0 :
> '/plugin/org.eclipse.wst.wsdl/model/WSDL.ecore#/';
> becomes:
> import wsdl_0 : 'WSDL.ecore#/';
>
> But, i have another problem:
> I created a dynamic instance from my bpel.ecore file with some
> activities. I tried to set for example the receive activity with some
> attributes like, operation, portType, which are normally in the WSDL
> file, but without success. When i try to validate the XMI file
> obviously it doesn't work, and displays that these features must be set.
>
> How to do this?
>
> Thanks in advance.
|
|
|
| Re: Problem when opening Ecore file with OCLInEcore using Juno [message #1069243 is a reply to message #1069155] |
Mon, 15 July 2013 09:53 |
| Eclipse User |
|
|
|
Hi,
I'm trying to test some OCL constraints, so i created a dynamic instance form the ecore model (in my case the ecore model of BPEL). For that, i opened the file with OCLInEcore editor, and right click, then create dynamic instance (it creates an XMI file). I created a BPEL process, with some activities namely, 'Receive', 'Reply', 'ASsign',,,,. In the properties view, you can set attributes of these activities. When i finished, i tried to validate the instance (right click, and validate), it displays problesms (reason: Diagnosis of process). It tells that some required features like 'portType',and 'operation' of the activities 'Reply' and 'Receive' in the BPEL process instance (in the XMI file) must be set.
In the properties view, when left click on a activity, say, 'Receive', it gives the possibility to set these attributes. But, when trying to do it, i noticed that it is expected a value from a list but nothing is found in the list, like the PortType name, or the Operation name. The editor is expected a value may be from another XMI file of the WSDL.ecore file, which represents an instance of a WSDL file (the wsdl of the BPEL process).
How can i get these properties, from another instance of WSDL.ecore?? if this is the case, how to get a property in a XMI file from another one??
Thanks in advance.
|
|
|
| Re: Problem when opening Ecore file with OCLInEcore using Juno [message #1069250 is a reply to message #1069243] |
Mon, 15 July 2013 10:13 |
| Eclipse User |
|
|
|
Hi
This is nothing to do with OCL; it's a basic EMF usage question.
Use "Load Resource..." from the context menu to load additional resources.
Regards
Ed Willink
On 15/07/2013 14:53, zernadji tarek wrote:
> Hi,
> I'm trying to test some OCL constraints, so i created a dynamic
> instance form the ecore model (in my case the ecore model of BPEL).
> For that, i opened the file with OCLInEcore editor, and right click,
> then create dynamic instance (it creates an XMI file). I created a
> BPEL process, with some activities namely, 'Receive', 'Reply',
> 'ASsign',,,,. In the properties view, you can set attributes of these
> activities. When i finished, i tried to validate the instance (right
> click, and validate), it displays problesms (reason: Diagnosis of
> process). It tells that some required features like 'portType',and
> 'operation' of the activities 'Reply' and 'Receive' in the BPEL
> process instance (in the XMI file) must be set.
> In the properties view, when left click on a activity, say, 'Receive',
> it gives the possibility to set these attributes. But, when trying to
> do it, i noticed that it is expected a value from a list but nothing
> is found in the list, like the PortType name, or the Operation name.
> The editor is expected a value may be from another XMI file of the
> WSDL.ecore file, which represents an instance of a WSDL file (the wsdl
> of the BPEL process).
>
> How can i get these properties, from another instance of WSDL.ecore??
> if this is the case, how to get a property in a XMI file from another
> one??
> Thanks in advance.
|
|
|
| Re: Problem when opening Ecore file with OCLInEcore using Juno [message #1069291 is a reply to message #1069243] |
Mon, 15 July 2013 11:52 |
| Eclipse User |
|
|
|
Populating references requires instances of the type that conform to the
reference's type. The entire resource set is visited to find such
instances, but if there are none, the list of choices will be empty.
You can use Load Resource... from the context menu to load other
resources, and if they contain instance of the type, those instances
will be appear in the list of choices. But BPEL has a specialized
editor and you're likely best of to use that editor for editing BPEL
instances...
On 15/07/2013 3:53 PM, zernadji tarek wrote:
> Hi,
> I'm trying to test some OCL constraints, so i created a dynamic
> instance form the ecore model (in my case the ecore model of BPEL).
> For that, i opened the file with OCLInEcore editor, and right click,
> then create dynamic instance (it creates an XMI file). I created a
> BPEL process, with some activities namely, 'Receive', 'Reply',
> 'ASsign',,,,. In the properties view, you can set attributes of these
> activities. When i finished, i tried to validate the instance (right
> click, and validate), it displays problesms (reason: Diagnosis of
> process). It tells that some required features like 'portType',and
> 'operation' of the activities 'Reply' and 'Receive' in the BPEL
> process instance (in the XMI file) must be set.
> In the properties view, when left click on a activity, say, 'Receive',
> it gives the possibility to set these attributes. But, when trying to
> do it, i noticed that it is expected a value from a list but nothing
> is found in the list, like the PortType name, or the Operation name.
> The editor is expected a value may be from another XMI file of the
> WSDL.ecore file, which represents an instance of a WSDL file (the wsdl
> of the BPEL process).
>
> How can i get these properties, from another instance of WSDL.ecore??
> if this is the case, how to get a property in a XMI file from another
> one??
> Thanks in advance.
|
|
|
Goto Forum:
Current Time: Sun Jul 06 21:32:05 EDT 2025
Powered by FUDForum. Page generated in 0.04406 seconds |
Home