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

[Thomas Diesler]

For your reference: https://jira.jboss.org/jira/browse/JBPM-2018

Could you please comment on the issue with the exact requirements that 
should actually be checked for. i.e. which jbpm fields does this issue 
apply to?

-thomas

Julian Coleman wrote:
> Hi,
> 
>> are you actually changing stuff at that level?
> 
> We don't make any changes here in the SOA platform build
> 
>> A change at that level is not cosmetic and effectively invalidates our QA.
> 
> Indeed.  So this change will require a re-test.
> 
>> Are you saying that this issue needs to be reopened?
> 
> Yes.  The previous SOA version had a length of 4000, so this one needs it as
> well.
> 
>> Here is the changeset that removed length="4000"
>> http://fisheye.jboss.org/changelog/JbpmSvn?cs=2440
> 
> Thanks for the pointer.  I've tried reversing the removal of the length 4000
> parts of that changeset, but the generated sql still has (e.g.) varchar(255)
> and nothing with length 4000, so I must be missing something.
> 
>> Maybe Alejandro can fill in the details why length="4000" was removed.
> 
> That might be useful.  Somehow, we need it back though ;-)
> 
> Thanks,
> 
> J
>