Generating the model does not work [message #7941] |
Tue, 22 May 2007 18:37 |
Eclipse User |
|
|
|
Originally posted by: ra_winter.web.de
Hi,
I need to extend the data model of the bpel designer with a number of
new activites as part of my diploma. Therefore tried to generate the
model, but either cannot be generated or the generated classes have
wrong imports. That's what I've done in the listed order:
Eclipse 3.2.2
EMF 2.2.3
WST 1.5.4
1. Installed a fresh eclipse environment with the plugin-versions
mentioned above.
2. Checked out the latest bpel-designer plugin packages from your CVS
3. Imported org.eclipse.emf.ecore, org.eclipse.xsd and
org.eclipse.wst.wsdl into workspace as binary projects (with visible
model folders)
4. Changed the model paths in plugins from /model to /src-wsdl/model and
/src-xsd/model, otherwise the bpel.ecore and bpel.genmodel files could
not be opened due to wrong paths.
5. Selected "Generate Model" while not changing anything in the model
itself!
6. Hundreds of compilation errors occured, because nearly all generated
classes import org.eclipse.wst.wsdl.impl.ExtensibilityElement (which is
simply not there) INSTEAD of
org.eclipse.wst.wsdl.internal.impl.ExtensibilityElement (which is
present in the org.eclipse.wst.wsdl plugin)
If I correct all these wrong imports manually and try to start the
bpel-designer plugin in a test environment, opening a .bpel-file results
in exceptions...
So now my questions, because I already spent a couple of days on that:
- What am I doing wrong? Are there special plugin-version I need to have
in order to get the model generation running?
- Where does the wrong import come from? I could not find anything if I
examine the ecore and genmodel files in text mode...
- Is this the only solution to extend the datamodel in order to support
new activites?
I hope these informations will help to find a solution for me...thanks
in advance!!!
Best regards,
Ralf Winter
|
|
|
Re: Generating the model does not work [message #7981 is a reply to message #7941] |
Tue, 22 May 2007 19:59 |
Michal Chmielewski Messages: 58 Registered: July 2009 |
Member |
|
|
This may have answered this in the dev group, but there is a slightly
screwed up way of dealing with EMF models especially those that "use
WSDL" emf models ...
Read this ...
http://dev.eclipse.org/mhonarc/lists/bpel-dev/msg00307.html
-michal
Ralf Winter wrote:
> Hi,
>
> I need to extend the data model of the bpel designer with a number of
> new activites as part of my diploma. Therefore tried to generate the
> model, but either cannot be generated or the generated classes have
> wrong imports. That's what I've done in the listed order:
>
> Eclipse 3.2.2
> EMF 2.2.3
> WST 1.5.4
>
> 1. Installed a fresh eclipse environment with the plugin-versions
> mentioned above.
> 2. Checked out the latest bpel-designer plugin packages from your CVS
> 3. Imported org.eclipse.emf.ecore, org.eclipse.xsd and
> org.eclipse.wst.wsdl into workspace as binary projects (with visible
> model folders)
> 4. Changed the model paths in plugins from /model to /src-wsdl/model and
> /src-xsd/model, otherwise the bpel.ecore and bpel.genmodel files could
> not be opened due to wrong paths.
> 5. Selected "Generate Model" while not changing anything in the model
> itself!
> 6. Hundreds of compilation errors occured, because nearly all generated
> classes import org.eclipse.wst.wsdl.impl.ExtensibilityElement (which is
> simply not there) INSTEAD of
> org.eclipse.wst.wsdl.internal.impl.ExtensibilityElement (which is
> present in the org.eclipse.wst.wsdl plugin)
>
> If I correct all these wrong imports manually and try to start the
> bpel-designer plugin in a test environment, opening a .bpel-file results
> in exceptions...
>
> So now my questions, because I already spent a couple of days on that:
>
> - What am I doing wrong? Are there special plugin-version I need to have
> in order to get the model generation running?
> - Where does the wrong import come from? I could not find anything if I
> examine the ecore and genmodel files in text mode...
> - Is this the only solution to extend the datamodel in order to support
> new activites?
>
> I hope these informations will help to find a solution for me...thanks
> in advance!!!
>
> Best regards,
>
> Ralf Winter
|
|
|
Re: Generating the model does not work [message #8017 is a reply to message #7981] |
Tue, 22 May 2007 20:26 |
Eclipse User |
|
|
|
Originally posted by: ra_winter.web.de
Hi Michal,
I already looked into this thread, but it was no solution for me. The
versions mentioned there did not work either.
Ralf
Michal Chmielewski schrieb:
> This may have answered this in the dev group, but there is a slightly
> screwed up way of dealing with EMF models especially those that "use
> WSDL" emf models ...
>
> Read this ...
>
> http://dev.eclipse.org/mhonarc/lists/bpel-dev/msg00307.html
>
> -michal
>
>
> Ralf Winter wrote:
>> Hi,
>>
>> I need to extend the data model of the bpel designer with a number of
>> new activites as part of my diploma. Therefore tried to generate the
>> model, but either cannot be generated or the generated classes have
>> wrong imports. That's what I've done in the listed order:
>>
>> Eclipse 3.2.2
>> EMF 2.2.3
>> WST 1.5.4
>>
>> 1. Installed a fresh eclipse environment with the plugin-versions
>> mentioned above.
>> 2. Checked out the latest bpel-designer plugin packages from your CVS
>> 3. Imported org.eclipse.emf.ecore, org.eclipse.xsd and
>> org.eclipse.wst.wsdl into workspace as binary projects (with visible
>> model folders)
>> 4. Changed the model paths in plugins from /model to /src-wsdl/model
>> and /src-xsd/model, otherwise the bpel.ecore and bpel.genmodel files
>> could not be opened due to wrong paths.
>> 5. Selected "Generate Model" while not changing anything in the model
>> itself!
>> 6. Hundreds of compilation errors occured, because nearly all
>> generated classes import
>> org.eclipse.wst.wsdl.impl.ExtensibilityElement (which is simply not
>> there) INSTEAD of
>> org.eclipse.wst.wsdl.internal.impl.ExtensibilityElement (which is
>> present in the org.eclipse.wst.wsdl plugin)
>>
>> If I correct all these wrong imports manually and try to start the
>> bpel-designer plugin in a test environment, opening a .bpel-file
>> results in exceptions...
>>
>> So now my questions, because I already spent a couple of days on that:
>>
>> - What am I doing wrong? Are there special plugin-version I need to
>> have in order to get the model generation running?
>> - Where does the wrong import come from? I could not find anything if
>> I examine the ecore and genmodel files in text mode...
>> - Is this the only solution to extend the datamodel in order to
>> support new activites?
>>
>> I hope these informations will help to find a solution for me...thanks
>> in advance!!!
>>
>> Best regards,
>>
>> Ralf Winter
|
|
|
Re: Generating the model does not work [message #8048 is a reply to message #7941] |
Wed, 23 May 2007 08:51 |
Eclipse User |
|
|
|
Originally posted by: ra_winter.web.de
I managed to re-generate the (original) model without any errors, except
that the constructor of CorrelationPattern always requires 3 parameters
and not two (for the out-in literal).
But when I load the plugins with the re-generated model into my runtime
environment, the following exception occurs when opening a BPEL file (it
worked without any problems before re-generating the model).
Is there any solution to this? I don't know where to start searching the
error cause...
Regards,
Ralf
java.lang.NullPointerException
at
org.eclipse.emf.ecore.impl.BasicEObjectImpl.eDerivedStructur alFeatureID(BasicEObjectImpl.java:1073)
at
org.eclipse.wst.wsdl.internal.impl.ExtensibleElementImpl.eGe t(ExtensibleElementImpl.java:137)
at
org.eclipse.emf.ecore.impl.BasicEObjectImpl.eGet(BasicEObjec tImpl.java:582)
at
org.eclipse.emf.ecore.impl.BasicEObjectImpl.eOpenIsSet(Basic EObjectImpl.java:863)
at
org.eclipse.emf.ecore.impl.BasicEObjectImpl.eDynamicIsSet(Ba sicEObjectImpl.java:850)
at
org.eclipse.emf.ecore.impl.BasicEObjectImpl.eDynamicIsSet(Ba sicEObjectImpl.java:838)
at
org.eclipse.wst.wsdl.internal.impl.ExtensibleElementImpl.eIs Set(ExtensibleElementImpl.java:210)
at
org.eclipse.emf.ecore.util.EContentsEList$FeatureIteratorImp l.hasNext(EContentsEList.java:414)
at
org.eclipse.emf.ecore.util.EContentAdapter.unsetTarget(ECont entAdapter.java:305)
at
org.eclipse.emf.ecore.util.EContentAdapter.unsetTarget(ECont entAdapter.java:282)
at
org.eclipse.emf.ecore.util.EContentAdapter.unsetTarget(ECont entAdapter.java:262)
at
org.eclipse.emf.common.notify.impl.BasicNotifierImpl$EAdapte rList.didRemove(BasicNotifierImpl.java:91)
at org.eclipse.emf.common.util.BasicEList.remove(BasicEList.jav a:922)
at
org.eclipse.emf.common.notify.impl.BasicNotifierImpl$EAdapte rList.remove(BasicNotifierImpl.java:143)
at org.eclipse.emf.common.util.BasicEList.remove(BasicEList.jav a:869)
at
org.eclipse.emf.common.notify.impl.BasicNotifierImpl$EAdapte rList.remove(BasicNotifierImpl.java:137)
at
org.eclipse.emf.ecore.util.EContentAdapter.removeAdapter(ECo ntentAdapter.java:349)
at
org.eclipse.emf.ecore.util.EContentAdapter.handleContainment (EContentAdapter.java:163)
at
org.eclipse.emf.ecore.util.EContentAdapter.selfAdapt(EConten tAdapter.java:68)
at
org.eclipse.emf.ecore.util.EContentAdapter.notifyChanged(ECo ntentAdapter.java:45)
at
org.eclipse.bpel.ui.ModelListenerAdapter.notifyChanged(Model ListenerAdapter.java:42)
at
org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify (BasicNotifierImpl.java:230)
at
org.eclipse.emf.common.notify.impl.NotifyingListImpl.dispatc hNotification(NotifyingListImpl.java:260)
at
org.eclipse.emf.common.notify.impl.NotifyingListImpl.clear(N otifyingListImpl.java:1072)
at
org.eclipse.emf.ecore.resource.impl.ResourceImpl.doUnload(Re sourceImpl.java:1209)
at
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doUnload(XMLR esourceImpl.java:496)
at
org.eclipse.emf.ecore.resource.impl.ResourceImpl.unload(Reso urceImpl.java:1228)
at
org.eclipse.bpel.common.ui.editmodel.ResourceInfo.dispose(Re sourceInfo.java:114)
at
org.eclipse.bpel.common.ui.editmodel.EditModel.releaseRefere nce(EditModel.java:197)
at
org.eclipse.bpel.common.ui.editmodel.EditModelClient.dispose (EditModelClient.java:111)
at
org.eclipse.bpel.ui.util.BPELEditModelClient.dispose(BPELEdi tModelClient.java:102)
at org.eclipse.bpel.ui.BPELEditor.dispose(BPELEditor.java:559)
at org.eclipse.bpel.ui.BPELEditor.init(BPELEditor.java:1690)
at org.eclipse.ui.internal.EditorManager.createSite(EditorManag er.java:842)
at
org.eclipse.ui.internal.EditorReference.createPartHelper(Edi torReference.java:583)
at
org.eclipse.ui.internal.EditorReference.createPart(EditorRef erence.java:372)
at
org.eclipse.ui.internal.WorkbenchPartReference.getPart(Workb enchPartReference.java:566)
at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:29 0)
at
org.eclipse.ui.internal.presentations.PresentablePart.setVis ible(PresentablePart.java:140)
at
org.eclipse.ui.internal.presentations.util.PresentablePartFo lder.select(PresentablePartFolder.java:268)
at
org.eclipse.ui.internal.presentations.util.LeftToRightTabOrd er.select(LeftToRightTabOrder.java:65)
at
org.eclipse.ui.internal.presentations.util.TabbedStackPresen tation.selectPart(TabbedStackPresentation.java:394)
at
org.eclipse.ui.internal.PartStack.refreshPresentationSelecti on(PartStack.java:1144)
at org.eclipse.ui.internal.PartStack.setSelection(PartStack.jav a:1097)
at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:13 11)
at org.eclipse.ui.internal.PartStack.add(PartStack.java:455)
at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:102 )
at org.eclipse.ui.internal.PartStack.add(PartStack.java:441)
at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:111 )
at
org.eclipse.ui.internal.EditorSashContainer.addEditor(Editor SashContainer.java:60)
at
org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorA reaHelper.java:217)
at
org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAre aHelper.java:207)
at
org.eclipse.ui.internal.EditorManager.createEditorTab(Editor Manager.java:822)
at
org.eclipse.ui.internal.EditorManager.openEditorFromDescript or(EditorManager.java:721)
at org.eclipse.ui.internal.EditorManager.openEditor(EditorManag er.java:682)
at
org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched( WorkbenchPage.java:2593)
at
org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(Workben chPage.java:2528)
at org.eclipse.ui.internal.WorkbenchPage.access$10(WorkbenchPag e.java:2520)
at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.ja va:2505)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:67)
at
org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPa ge.java:2500)
at
org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPa ge.java:2485)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:388)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:350)
at
org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInE ditor(EditorUtility.java:275)
at
org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInE ditor(EditorUtility.java:139)
at
org.eclipse.jdt.internal.ui.actions.OpenActionUtil.open(Open ActionUtil.java:49)
at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:19 0)
at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:17 4)
at
org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchR un(SelectionDispatchAction.java:267)
at
org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(Selec tionDispatchAction.java:243)
at
org.eclipse.jdt.internal.ui.packageview.PackageExplorerActio nGroup.handleOpen(PackageExplorerActionGroup.java:306)
at
org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$ 4.open(PackageExplorerPart.java:653)
at
org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredV iewer.java:817)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.runtime.Platform.run(Platform.java:843)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:14 9)
at
org.eclipse.jface.viewers.StructuredViewer.fireOpen(Structur edViewer.java:815)
at
org.eclipse.jface.viewers.StructuredViewer.handleOpen(Struct uredViewer.java:1069)
at
org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(Stru cturedViewer.java:1168)
at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrate gy.java:249)
at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.ja va:243)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrate gy.java:283)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3348)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2968)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1930)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1894)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:422)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:95)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:78)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:92)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:68)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:400)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:177)
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.core.launcher.Main.invokeFramework(Main.java:336 )
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at org.eclipse.core.launcher.Main.main(Main.java:952)
|
|
|
|
Powered by
FUDForum. Page generated in 0.04054 seconds