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

[Thomas Diesler]

Hi Julian,

are you actually changing stuff at that level?

We verify jBPM functionality and database backward compatibility with 
the hibernate mapping that is in place for a given version. We also 
generate SQL update scripts from those if needed.

A change at that level is not cosmetic and effectively invalidates our QA.

Are you saying that this issue needs to be reopened?

StringInstance hbm configuration column length of 4000
https://jira.jboss.org/jira/browse/JBPM-1109

Here is the changeset that removed length="4000"
http://fisheye.jboss.org/changelog/JbpmSvn?cs=2440

Maybe Alejandro can fill in the details why length="4000" was removed.

-thomas

Julian Coleman wrote:
> Hi,
> 
>> 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.
> 
> There is another blocking JIRA for SOA 4.3.0 CP01/jBPM 3.2.5 SP1 - SOA-1164.
> This is a new incarnation of the bug orginally discussed in SOA-271,
> JBESB-1435 and JBPM-1109.
> 
> I am testing a build with the fix from JBPM-1109 applied to:
> 
>   modules/core/src/main/resources/org/jbpm/context/exe/variableinstance/StringInstance.hbm.xml
> 
> but I am unsure if:
> 
>   modules/core/src/main/resources/org/jbpm/context/exe/variableinstance/HibernateStringInstance.hbm.xml
>   modules/core/src/main/resources/org/jbpm/context/log/variableinstance/StringUpdateLog.hbm.xml
> 
> also need to be changed (or, indeed, if I have missed another location).  Any
> help/confirmation appreciated.  We can't tag SP1 until this is fixed.
> 
> Thanks,
> 
> J
>