| Develop new plugins from the BPEL designer source code [message #559335] |
Thu, 16 September 2010 08:11  |
Jindo Messages: 2 Registered: September 2010 |
Junior Member |
|
|
Dear all,
I have checked out the BPEL designer source codes from the repository ":pserver:anonymous@dev.eclipse.org:/cvsroot/technology".
I would like to add a function and rebuild(or compile or deploy, whatever) these source codes into BPELxx designer plugins for testing my created function working with the BPEL.
Could you please tell me how to rebuild and test the BPEL plugins from their source code ?
Thank you,
|
|
|
| Re: Develop new plugins from the BPEL designer source code [message #559422 is a reply to message #559335] |
Thu, 16 September 2010 11:08   |
|
Hi Jindo,
I'm assuming you will eventually want to build a deployable product? We are currently working on setting up nightly builds at build.eclipse.org (you may have seen the pom.xml maven project files). This should be running by end of this week, but in the meantime you can build and run the BPEL Designer plugins from you eclipse IDE.
You should be able to run the current source code with eclipse 3.6 - the "Eclipse IDE for Java EE Developers" distribution has everything you need.
Let me know if you have problems getting started.
BTW, can I ask what kind of extensions you are building on to the editor? Have you considered contributing your work to the BPEL Designer project? 
Bob
|
|
|
|
| Re: Develop new plugins from the BPEL designer source code [message #628673 is a reply to message #559661] |
Thu, 23 September 2010 11:53  |
|
Hi jindo,
Sorry for the late reply - didn't see your updated post here...
I'm still not quite sure what you're trying to do - from your description it sounds like you are trying to do the same thing the editor already does, except packaged into an RCP.
To answer your questions about extension points exposed by the editor, these are described in detail here. These allow you to extend the editor's functionality by defining BPEL language extensions.
There are basically 4 "components" to the BPEL Designer: 1. an extensible EMF model that implements the WS-BPEL 2.0 specification; 2. a UI (the editor itself); 3. an extensible validation framework for WS-BPEL 2.0; and 4. deployment editor and components for deploying to a BPEL runtime. Beyond that, the editor itself is not really meant to be broken apart and pieced together.
Maybe if I understood better the problem you're trying to solve, I could suggest a way to attack this.
Bob
|
|
|
Powered by
FUDForum. Page generated in 0.01658 seconds