[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [bpel-dev] RE: BPEL plugin list
|
Michal,
I totally agree - the WSDL dependency story seems not optimized ... to say
the least.
Even worse is that the WSDL model in WTP 1.5x PRETENDS to use EMF 2.2, but
really use EMF 2.1 ... you can tell from the fact the code is generated.
Good news is that I already talked to the WSDL guys because of that, and
they told me that we'll get a EMF 2,3 - based model by WTP 2.0 M6.
Let me know if you have further requests that we should redirect towards
them.
Thanks
Simon
Simon Moser, M.Eng. Mail: IBM Deutschland
smoser@xxxxxx Entwicklung GmbH
Team Lead BPEL Editor / .com Vorsitzender des
Websphere Integration Phone: Aufsichtsrats: Johann
Developer +49-7031-16-4 Weihen
Dept. 4722, Bldg. 71032-01, 304 Geschäftsführung: Herbert
Room 086 Fax: Kircher
Websphere Solutions and +49-7031-16-4 Sitz der Gesellschaft:
Services 890 Böblingen
IBM Deutschland Entwicklung Registergericht:
GmbH Amtsgericht Stuttgart, HRB
Schönaicherstr. 220, D – 243294
71032 Boeblingen
Michal
Chmielewski
<michal.chmielews To
ki@xxxxxxxxxx> "BPEL Designer project developer
Sent by: discussions."
bpel-dev-bounces@ <bpel-dev@xxxxxxxxxxx>
eclipse.org cc
Subject
03/07/2007 11:57 Re: [bpel-dev] RE: BPEL plugin list
PM
Please respond to
"BPEL Designer
project developer
discussions."
<bpel-dev@eclipse
.org>
Mchael,
This bothered me from the beginning .... it requires a few magical moves to
get the generation bit going. Not to mention that our own BPEL model is not
usable down the stream as well (because of that goofy WSDL dependency).
Yikes.
I've spent a few hours educating myself on the mysteries involved and here
is what I found:
1) The XSD model is in plugin org.eclipse.xsd and is made available via the
extension point
org.eclipse.emf.ecore.generated_package
I have re-pointed the references to this model in from our BPEL model so
that the references are
platform:/plugin/org.eclipse.xsd/model/....
One addition thing is that the XSD model embedded in the plugin can be
browsed from the ECore editor.
If you go to Ecore Editor menu and choose Load Resource ... you can browse
registered packages and find the XSD model there.
2) The WSDL model is in plugin org.eclipse.wst.wsdl but as of version 1.5.3
this is not usable as a "referenced" model as it exists in the plugin.
Which kinda sucks well simply because of the ExtensibilityElement ... we
need that in the BPEL model ... and anyone that wishes to extend WSDL
through this mechanism will need it. If you try to open the wsdl.ecore from
that plugin you are OK until you venture to something that references XSD
for instances. Then you get this ....
java.io.FileNotFoundException:
..\..\..\org.eclipse.xsd\src-xsd\model\XSD.ecore (The system cannot find
the path specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at
org.eclipse.emf.ecore.resource.impl.URIConverterImpl.createFileInputStream(URIConverterImpl.java:469)
Which means that in the wsdl.ecore they use the src-* references to the XSD
ecore. This makes it unusable for code generation ... and I am not sure why
I would need the source to the wsdl plugin to just be able to generate the
source for my model. This seems sorta screwed ...
.... but the good news is that this a well known issue ...
https://bugs.eclipse.org/bugs/show_bug.cgi?id=145413
Have you guys had anything to do with this ? It looks like it will appear
in WTP 2.0 M6.
At that point we ought to probably consider moving our stuff in that
direction.
Michael Illiger2 wrote:
Hi
The problem with WST is that they require EMF 2.2.x but created their
WSDL model with an older Version (probably EMF 2.1.x). It seems as
EMF has changed some things in the way they create their model code -
that means that a EMF 2.2 or above BPEL model simply doesn't work
together with the EMF 2.1 WSDL model from WST.
Our solution was to use two different eclipse installations.
One with a model creation configuration:
- eclipse SDK 3.2.1
- EMF SDK 2.1.2
- WST SDK 1.5.2
plugins in workspace are
- org.eclipse.bpel.model
- org.eclipse.wst.wsdl (with fixed source folder)
- org.eclipse.xsd (with fixed source folder
and another one for real developing. The modified model plugins have
to be copied by hand (or you might even try to use the same workspace
for both configurations...)
I remember some bug concerning CorellationPattern. Just add/remove
any parameters that do not fit...
mit freundlichen Grüßen / best regards
Michael Illiger
-----------------------------------------------------------------
Business Process Solutions Development 1
IBM Boeblingen Laboratory
Dept. 4722, Bldg. 71032-01, Room 086
Phone: +49 7031-16-1273
E-Mail: milliger@xxxxxxxxxx
-----------------------------------------------------------------
IBM Deutschland Entwicklung GmbH
Vorsitzender des Aufsichtsrats: Johann Weihen
Geschäftsführung: Herbert Kircher
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
Rafael Llarena Gomez
<rafael.llarena@xxxxxxxxxxxxxx>
Sent by:
bpel-dev-bounces@xxxxxxxxxxx To
"BPEL Designer project
developer discussions."
02/22/2007 10:48 AM <bpel-dev@xxxxxxxxxxx>
cc
Please respond to Subject
"BPEL Designer project developer RE: [bpel-dev] RE: BPEL
discussions." plugin list
<bpel-dev@xxxxxxxxxxx>
Hi Michael,
I’ve tried to install the same configuration you are using, but it
does not work. It says (and the WST page confirms it) that to install
WST SDK 1.5.2 it is required EMF 2.2.X.
So, changing the configuration to an older WST so I can use EMF
2.1.2, I get compilation errors in CorrelationPattern, because of the
constructor of AbstractEnumerator, which only uses three parameters
in EMF 2.2.X onwards. Are you really using EMF 2.1.2? Maybe I am
doing something wrong.
Rafael Llarena
From: bpel-dev-bounces@xxxxxxxxxxx [
mailto:bpel-dev-bounces@xxxxxxxxxxx] On Behalf Of Michael Illiger2
Sent: miércoles, 21 de febrero de 2007 16:29
To: BPEL Designer project developer discussions.
Subject: Re: [bpel-dev] RE: BPEL plugin list
Hei Rafael
one of the major problems I faced last time I created the BPEL model
was that the WSDLecore cannot resolve any XSD references because the
pathes they use in there are simply wrong. So either adopt all pathes
in the wsdl ecore or modify the source folder in the xsd plugin.
Same thing with BPEL and WSDL: Some references are wrong and cannot
be resolved... Either modify pathes in BPEL ecore or modify source
folder in WSDL.
Here's my eclipse configuration I use to modify the BPEL model:
- eclipse SDK 3.2.1
- EMF SDK 2.1.2
- WST SDK 1.5.2
hope this helps...
regards Michael
-----------------------------------------------------------------
Business Process Solutions Development 1
IBM Boeblingen Laboratory
Dept. 4722, Bldg. 71032-01, Room 086
Phone: +49 7031-16-1273
E-Mail: milliger@xxxxxxxxxx
-----------------------------------------------------------------
IBM Deutschland Entwicklung GmbH
Vorsitzender des Aufsichtsrats: Johann Weihen
Geschäftsführung: Herbert Kircher
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
Rafael Llarena Gomez
<rafael.llarena@atosorigi
n.com>
Sent by: To
bpel-dev-bounces@eclipse. Michal Chmielewski
org <michal.chmielewski@xxxxxxxxxx>, "BPEL
Designer project developer
discussions." <bpel-dev@xxxxxxxxxxx>
02/21/2007 04:01 PM cc
Simon D Moser/Germany/IBM@IBMDE
Subject
[bpel-dev] RE: BPEL plugin list
Please respond to
"BPEL Designer project
developer discussions."
<bpel-dev@xxxxxxxxxxx>
Dear Michael and Simon,
Thank you for your answer.
I’ve imported the WSDL and XSD models that come with the
wtp-all-in-one eclipse distribution I’m using. In fact, I can open
the XSD and WSDL ecore and genmodel files and there are no errors. So
I don’t know where the problem is.
I’ll keep researching, but maybe you have faced this problem before.
Best regards,
Rafael Llarena
You need the WSDL and XSD ecore models to not have this problem.
Simon probably knows this ....
Simon, what plugins have these source files ?
I noticed that I can't find the ecore models for WSDL and XSD in my
eclipse distro. I've found them in the plugins in the CVS repository
but I think they are "slightly" different than what we have been
using.
-michal
Rafael Llarena Gomez wrote:
Hello,
I’m interested in the BPEL Eclipse plug-in. I’m subscribed to the
distribution list. I’ve tried to send a message but it has been
bounced twice (is it a restricted list?).
I’ve found this problem and I don’t know if you can help me.
I’ve tried to make a little modification in the bpel model. I make
the changes in the bpel.ecore, and they are applied to the
bpel.genmodel. But The options of “Generate” are not enabled so I
can’t execute them. I’ve seen that, when opening the bpel.genmodel,
this exception is raised, so I guess the problem might be related:
(If this is not the appropriate channel for this, sorry for the
inconvenience)
eclipse.buildId=M20060921-0945
java.version=1.4.2_12
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=es_ES
Command-line arguments: -os win32 -ws win32 -arch x86
Warning
Tue Feb 20 17:25:12 CET 2007
java.lang.NullPointerException
at
org.eclipse.emf.codegen.ecore.genmodel.impl.GenBaseImpl.findGenPackageHelper(GenBaseImpl.java:802)
at
org.eclipse.emf.codegen.ecore.genmodel.impl.GenBaseImpl.findGenPackage(GenBaseImpl.java:874)
at
org.eclipse.emf.codegen.ecore.genmodel.impl.GenModelImpl.computeMissingUsedGenPackages(GenModelImpl.java:5794)
at
org.eclipse.emf.codegen.ecore.genmodel.impl.GenModelImpl.reconcile(GenModelImpl.java:5762)
at
org.eclipse.emf.codegen.ecore.genmodel.presentation.GenModelEditor.initialize(GenModelEditor.java:391)
at
org.eclipse.emf.codegen.ecore.genmodel.presentation.GenModelEditor.createPages(GenModelEditor.java:693)
at
org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:276)
at
org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:596)
at
org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:372)
at
org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:566)
at
org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:214)
at
org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2595)
at
org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2528)
at
org.eclipse.ui.internal.WorkbenchPage.access$10(WorkbenchPage.java:2520)
at
org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2505)
at
org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
at
org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2500)
at
org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.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.openInEditor(EditorUtility.java:275)
at
org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:139)
at
org.eclipse.jdt.internal.ui.actions.OpenActionUtil.open(OpenActionUtil.java:49)
at
org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:190)
at
org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:174)
at
org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:267)
at
org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:243)
at
org.eclipse.jdt.internal.ui.packageview.PackageExplorerActionGroup.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(StructuredViewer.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:149)
at
org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:815)
at
org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1069)
at
org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1168)
at
org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:249)
at
org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:243)
at
org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.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.java:3348)
at
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
at
org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
at
org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
at
org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at
org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.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(EclipseStarter.java:400)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
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)
--
Rafael Llarena Gómez
--
Michal Chmielewski, CMTS, Oracle Corp,
W:650-506-5952 / M:408-209-9321
"Manuals ?! What manuals ? Son, it's Unix, you just gotta know."
_______________________________________________
bpel-dev mailing list
bpel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/bpel-dev
_______________________________________________
bpel-dev mailing list
bpel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/bpel-dev
_______________________________________________
bpel-dev mailing list
bpel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/bpel-dev
--
Michal Chmielewski, CMTS, Oracle Corp,
W:650-506-5952 / M:408-209-9321
"Manuals ?! What manuals ? Son, it's Unix, you just gotta know."
_______________________________________________
bpel-dev mailing list
bpel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/bpel-dev
