topic HistoricDetailVariableInstanceUpdateEntity can not deserialize value using custom ClassLoader in Alfresco Archive

HistoricDetailVariableInstanceUpdateEntity can not deserialize value using custom ClassLoader

smokemaker — Mon, 14 Jul 2014 15:30:53 GMT

Hi all!Help me, please, with custom ClassLoader in ProcessEngineConfigurationImplThe issue can be seen on Activiti 5.13 under Alfresco.In org.alfresco.repo.workflow.activiti.ActivitiWorkflowEngine.endNormalTask:taskService.complete(localTaskId);// The task should have a historicTaskInstanceHistoricT

Re: HistoricDetailVariableInstanceUpdateEntity can not deserialize value using custom ClassLoader

trademak — Mon, 21 Jul 2014 10:23:40 GMT

That looks like a bug indeed. I think the best place to raise the issue would be with Alfresco (community or enterprise).

Best regards,

Re: HistoricDetailVariableInstanceUpdateEntity can not deserialize value using custom ClassLoader

smokemaker — Mon, 21 Jul 2014 11:06:54 GMT

Tijs, thanks for your reply!

But do you think the Alfresco code should be modified? It seems that Alfresco just uses the Activiti API via HistoryService. Or do they use it in improper way?

Thank you!

Serge

Re: HistoricDetailVariableInstanceUpdateEntity can not deserialize value using custom ClassLoader

jbarrez — Fri, 25 Jul 2014 07:00:16 GMT

The Alfresco integration is in a very particular way implemented. That's why Tijs pointed out it's rather on the Alfresco side.

Re: HistoricDetailVariableInstanceUpdateEntity can not deserialize value using custom ClassLoader

frederikherema1 — Fri, 25 Jul 2014 07:24:47 GMT

This is already fixed in current Activiti-releases, having all serialisable variables touched (value cached in the variable instance) before leaving the command-context, when getting them. Unfortunately, this fix is not yet part of the current Alfresco release.

This can be fixed in the Alfresco code as well, IMHO. So best to create an issue, as Tijs suggested.