Activiti 5.11: wrong historicDetailResultMap_postgres

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

xandros

Hi,

After upgrade to Activiti 5.11 the query:

List<HistoricDetail> hds = historyService.createHistoricDetailQuery().processInstanceId(processInstanceId).variableUpdates().orderByTime().desc().list();
‍‍‍

return HistoricDetail that not implements HistoricVariableUpdate , then is impossible access variable informations (via cast).

I use POSTGRES as DB and I think only this db is affected, indeed after some investigation I found a problem in HistoricDetail.xml:

The "createHistoricDetailQuery" use "historicDetailResultMap" that in case of POSTGRES is remapped to "historicDetailResultMap_postgres".
In "historicDetailResultMap_postgres" definition there is:

<discriminator javaType="string" column="TYPE_">
      <case value="VariableUpdate" resultMap="historicVariableUpdateResultMap_postgres"/> 
      <case value="FormProperty" resultMap="historicFormPropertyResultMap"/> 
</discriminator>
‍‍‍‍‍‍

but "historicVariableUpdateResultMap_postgres" is not defined, then the MyBatis fails to map data.

My workaround is change "historicVariableUpdateResultMap_postgres" in "historicVariableUpdateResultMap" that is defined after in HistoricDetail.xml.

<discriminator javaType="string" column="TYPE_">
      <case value="VariableUpdate" resultMap="historicVariableUpdateResultMap"/> 
      <case value="FormProperty" resultMap="historicFormPropertyResultMap"/> 
</discriminator>
‍‍‍‍‍‍

Now query works and is possible to cast returned HistoricDetail to HistoricVariableUpdate.

Can you apply patch on next release please?

Best regards!

frederikherema1

Hi, thanks for reporting this. I stumbled upon this issue today an will get it fixed asap…

https://jira.codehaus.org/browse/ACT-1512