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

[Alejandro Guizar]

Hi Julian, please read my comments below.

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.

Since 3.2.4 the jBPM user guide contains a new chapter on application
server facilities. I also removed the old content on the subject. Let me
know if I can help further in the documentation area.

> > 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?

Before you do, I want to run a test matrix against the 3.2.5 SP branch
without version columns. If it passes, then we can confidently provide
our customers a jBPM build that will not produce optimistic locking
exceptions.

> Thanks,
> 
> J
>