[jbpm-dev] Re: jbpm-3.2.5.SP

[Thomas Diesler]

After you've taken the stuff back out again, could you please start 
another QA build for 3.2.5.SP? We can can only tag from a clean QA build.

cheers
-thomas

Alejandro Guizar wrote:
> Update to my previous email: I ran the test matrix against 3.2.5 SP with
> version columns commented out. Several tests having some form of
> concurrency failed. 
> 
> http://jbpm.dyndns.org:8180/hudson/job/jBPM3-Database-Matrix/1/
> 
> Without version checking, a job may get executed more than once. Hence
> pure pessimistic locking is not possible, at least not the way jobs are
> acquired currently.
> 
> Please go ahead and tag 3.2.5 SP1. I will take JBPM-1953 out of that
> release and discuss the alternatives with Thomas.
> 
> -Alejandro
> 
> El mié, 04-02-2009 a las 14:48 +0000, Julian Coleman escribió:
>> Hi,
>>
>> Thanks for looking at these.
>>
>>> Today I ported JBPM-1903 to 3.2.5.SP because it was relevant to the
>>> upcoming migration to JMS. 
>>>
>>> Regarding JBPM-1452, the enterprise services have to be enabled in the
>>> SOA-P jBPM configuration file. I made a few remarks to Jiri's setup
>>> instructions directly in JIRA.
>> For this, we just need to update our JBPM Reference Guide to take into
>> account these changes.
>>
>>> As for JBPM-1453, the feature requested there is unfeasible. We cannot
>>> disable optimistic locking with a switch. We would need an alternate JAR
>>> with no version columns declared in the mapping files.
>> So, we won't get a fix for this for SOA 4.3.0 CP01.  Are there any other
>> issues that need to be pulled up to the JBPM 3.2.5 SP branch?  If not, can
>> we tag 3.2.5 SP1 and build the next SOA release candidate from it?
>>
>> Thanks,
>>
>> J
>>
>