[bpel-dev] Collaboration with Apache ODE [WAS: Re: Feedbacks]

["Matthieu Riou" <matthieu@xxxxxxxxxxxxx>]

Hi,

I'm taking this opportunity to uncloak and propose some help :) If you need more information on how to better integrate with the ODE compiler or deploy processes, feel free to ask on dev@xxxxxxxxxxxxxx, we'll be happy to help, provide some code examples or pointers to existing code. Also if you're experiencing issues with the ODE compiler or runtime, we can discuss what could be improved.

In any case, we're happy to collaborate :)

Cheers,
Matthieu

On Thu, May 29, 2008 at 2:16 AM, Simon D Moser <SMOSER@xxxxxxxxxx> wrote:

Hi Pierre,

the charter of the project basically requires us to show a "reference
runtime integration". Now since this is a multi-party project, we sort of
agreed on the fact that we will show that "reference runtime" to be Apache
ODE. Having said that, there has been works in the past by Bruno Wassermann
in London who wrote an integration to the ActiveBPEL engine. This basically
means: there is a common runtime integration framework that is part of the
official project. Then there is an ActiveBPEL integration  (which is not
part of the official project), an Apache ODE integration (which is not
complete yet, but will be an official part of the project), and obviously
you can write an integration for Orchestra (again, probably not part of the
official project).

"Official part" here means that we won't package and ship the plugins as
part of a BPEL Designer Release.

As for you last question - how to become a committer: This is the standard
eclipse procedure. This means: You fix bugs (e.g. by attaching patches to
bugzilla) or you make code contributions to the project, and then one
existing committer can initiate a nomination process. If then a majority of
the existing committers agree the person gets the committer status. In
other words: You have to prove your talent first before you can become a
committer ;-)

Cheers
Simon

Simon Moser, M.Eng.



 Websphere Integration       Mail:           IBM Deutschland Entwicklung
 Developer Development       smoser@xxxxxx.  GmbH
 Team Lead BPEL Editor       com             Vorsitzender des
 Dept. 4722, Bldg.           Phone:          Aufsichtsrats: Martin Jetter
 71032-01, Room 086          +49-7031-16-43  Geschäftsführung: Herbert
 Websphere Solutions and     04              Kircher
 Services                    Fax:            Sitz der Gesellschaft:
 IBM Deutschland             +49-7031-16-48  Böblingen
 Entwicklung GmbH            90              Registergericht: Amtsgericht
 Schönaicherstr. 220, D –                    Stuttgart, HRB 243294
 71032 Boeblingen













 From:       Pierre Vigneras <pierre.vigneras@xxxxxxxx>

 To:         bpel-dev@xxxxxxxxxxx

 Date:       27.05.2008 15:52

 Subject:    Re: [bpel-dev] Feedbacks






Le Monday 19 May 2008 18:00:27 bpel-dev-request@xxxxxxxxxxx, vous avez
écrit :
> Message: 2
> Date: Mon, 19 May 2008 14:48:19 +0200
> From: Simon D Moser <SMOSER@xxxxxxxxxx>
> Subject: Re: [bpel-dev] Feedbacks
> To: "BPEL Designer project developer discussions."
>            <bpel-dev@xxxxxxxxxxx>
> Cc: bpel-dev@xxxxxxxxxxx, bpel-dev-bounces@xxxxxxxxxxx
> Message-ID:
>
<OF091E7360.3284201B-ONC125744E.0044959D-C125744E.004657A8@xxxxxxxxxx>
> Content-Type: text/plain; charset=UTF-8
>
> Hello Pierre,
>
> welcome! Let me try to answer your questions:

Sorry for the delay...

> Re 1.) The correlation bug, I think, is not fixed. I just tried the
> If-Elseif-issue on the trunk and IMHO this is correct. We are still on
CVS
> rather than SVN ;-)

Ok. CVS is also fine for us, its open-source! ;-)

> In the Trunk, you can also add a FaultHandler to the Process. Give it a
try
> please ;-)

I am currently downloading all the required libraries in a separate fresh
Eclipse development environment...
I will give it  a try.

> Re 2.) As currently stated, the BPEL Designer is about to Release M4
(last
> missing piece is a runtime integration).

Well, what do you mean by runtime integration? We have an open-source BPEL
engine
Orchestra (see: http://orchestra.objectweb.org/). It would be great if the
BPEL editor can integrate
smoothly with our BPEL engine. This is definitely one area where we can
provide help and support.

Tell us what is missing, and if Orchestra can be an integration target.

> Re 3.) You certainly can access the cvs "trunk" (its called HEAD there;-)
> ;-) http://www.eclipse.org/bpel/install.php - step 3 gives you the
> necessary data.

Done. Thanks.

> Re 4.) Absolutely. Any particular piece you are interested on to work on
?

Well, runtime integration with Orchestra is definitely an interesting point
for us.

> I mean there are a few bugs that need to be addressed (one could just
> provide patches), but also in case you want to do some functional
> enhancement - feel free to propose it. Feel free to contact me to engage
in
> further discussions on the "how".

Can we gain a committer access? How? What is the  procedure?

Regards.

--
Pierre Vignéras
Bull, Architect of an Open World TM
*BPM Team*, Bull R&D
1, rue de Provence
38130 Echirolles (France)
Direct Line: +33-4-76-29-74-06

*Orchestra*, The BPEL open source project: http://orchestra.objectweb.org
*Bonita*, The XPDL open source project: http://bonita.objectweb.org
_______________________________________________
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