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: [email protected] 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 > >
