My main point was to keep a way to use a BPEL engine without using the standard JBI packaging. This can be useful for people who are embedding ServiceMix in a web application for example.
However, having to maintain the whole bpel engine inside ServiceMix is not imho a very good solution. I' d rather enhance the one in ode trunk to leverage ServiceMix features, but i bet the ode community will want it to be JBI implementation independant (which would be a good thing). So the other way may be to write another JBI component specific to ServiceMix which would be able to be configured using xbean, which could leverage xa transactions (this is not really covered in the jbi spec), and provide some other nice features, such as EPR resolution using ServiceMix, etc ... Note that these features do not necesseraly make the component non portable, but it may not work the same way in other JBI containers.... On 8/17/06, Grant McDonald <[EMAIL PROTECTED]> wrote:
That's probably not too bad an idea since Guillaume was still wanting to support a lightweight BPEL implementation. What's the consensus on what will happen (or not happen) with BPE? -----Original Message----- From: cory [mailto:[EMAIL PROTECTED] Sent: Thursday, 17 August 2006 5:08 AM To: ode-dev@incubator.apache.org Subject: Re: Commented code in StartCatchAction I don't know what happens to the scratch area. I guess it will probably just get deleted someday. Maybe ServiceMix could take it in under the servicemix-bpe component :-) -cory On 8/16/06, Grant McDonald <[EMAIL PROTECTED]> wrote: > The integration layer in servicemix uses a ThreadLocal to store a reference > to the BPEEndpoint before it calls the event director. After the execution > of the business process (i.e. when the event director returns) the > ThreadLocal variable is set back to null. Normally this isn't an issue but > in the case where the you have a receive/reply busines process and the last > statement is an InOnly MEP invoke the event director thread returns before > the invoke has filtered out to the integration layer at which point it tries > to access the ThreadLocal which has already been set to null. > > So what is the plan for BPE? Is it going to gather dust? (Not that I am > really concerned) I'd like to know which way I should direct future efforts > (testing, fixing bugs, proposing enhancements etc.. ;) Should I just be > concentrating on the trunk now? > > -----Original Message----- > From: cory [mailto:[EMAIL PROTECTED] > Sent: Thursday, 17 August 2006 12:44 AM > To: ode-dev@incubator.apache.org > Subject: Re: Commented code in StartCatchAction > > > Can you describe the race condition? > > You might want to consider looking at the Ode trunk. There is really > no merge going on the Ode trunk is basically PXE. > > -cory > > On 8/15/06, Grant McDonald <[EMAIL PROTECTED]> wrote: > > Hi, > > > > Can someone tell me what the current status of the new merged trunk is wrt > > the jbi componentization? Is there still a lot of work to do in this area > > before it becomes useable? The reason I ask is that I have come across a > > race condition in the current ServiceMix integration layer with BPE and am > > trying to gauge the whether it's worth the time to fix or if it should be > > postoned in favour of using the new merged ODE. > > > > Thanks in advance, > > > > Grant McDonald > > > > > >
-- Cheers, Guillaume Nodet
