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.
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.
-Alejandro
El mar, 03-02-2009 a las 16:30 +0000, trevor kirby escribió:
Thanks for the branch and the work so far guys. The two issues
mentioned below are now a blocker for the SOA CP because of NTT, so I
would appreciate it if you could get the fixes into the 3.2.5 sp branch
as quickly as you can. I've included Julian Coleman on the CC, can you
make sure you include him on any emails about these JIRA's or NTT.
Trev
> Hi Alejandro,
>
> thanks for all you effort to keep the jbpm3 code base in prime shape
>
>
http://jbpm.dyndns.org:8280/hudson/job/jBPM3-Container-Matrix/
>
> After a conversation with Trevor, I created a jbpm-3.2.5.SP1 branch
> that is going to take the place of 3.2.4.SP1 in the SOA platform. The
> benefit is that we don't have to merge stuff back to 3.2.4.SP that was
> already fixed in 3.2.5.GA.
>
> I already merged the changes from 3.2.4.SP to 3.2.5.SP there there is
> (hopefully) nothing more for you to do.
>
> Trevor also mentioned the importance of NTT issues again.
>
>
https://jira.jboss.org/jira/browse/JBPM-1952
>
https://jira.jboss.org/jira/browse/JBPM-1953
>
> Perhaps you could have a look at those next and if possible also apply
> the necessary changes to 3.2.5.SP?
>
> The jbpm-3.2.5.SP QA is here
>
>
http://jbpm.dyndns.org:8180/hudson
>
> cheers
> -thomas