topic DeployCmd (and other Commands) not Serializable in Alfresco Archive

DeployCmd (and other Commands) not Serializable

retourfer — Wed, 18 Apr 2012 15:12:54 GMT

Hiwe want to integrate Activiti Workflow Engine in our Client/Server application. This means the activity engine is running in the server application and the user interface is implemented in an Eclipse RCP application. The remoting is done with Spring HttpInvoker.I was able to access the process eng

Re: DeployCmd (and other Commands) not Serializable

trademak — Thu, 19 Apr 2012 13:42:17 GMT

Hi,

The JIRA issue you are referring to fixed StartProcessInstanceCmd I think.
It would be easy to add this to the DeployCmd as well. Do you need other commands?

Best regards,

Re: DeployCmd (and other Commands) not Serializable

retourfer — Thu, 19 Apr 2012 14:10:03 GMT

Hi

currently i only need the DeployCmd but i found some more commands which have serialVersionUID = 1L specified but do not implement Serializable interface.
- AcquireJobsCmd
- DeleteJobsCmd
- GetNextIdBlockCmd

But with the change in DeployCmd i can then deploy a new process definition.

The next problem then comes up if i try to start a new process instance RuntimeService.startProcessInstanceById(id) because the returned ProcessInstance object is also not serializable and i think there will be a lot more classes which are not serializable.

So therefore my questions:
Did somebody already run the activity engine in a distributed environment and if yes how?
Is running activity engine in a client/server environment a scenario which should be supported but does not yet work properly?

Re: DeployCmd (and other Commands) not Serializable

trademak — Thu, 19 Apr 2012 14:24:59 GMT

Hi,

Right, the REST API would be the default choice for that. Would that work for you?
I haven't heard of any client/server apps that bypass the REST API.

Best regards,

Re: DeployCmd (and other Commands) not Serializable

retourfer — Fri, 20 Apr 2012 09:54:57 GMT

Hi

i think i found a solution to make it working without using the REST API. To try now with it i have no time yet.

I used converters on the server side for some not serializable data types like ProcessInstance, StartFormData, … which convert their attributes into a serializable implementation of the interface.

But i use some more classes to be made serializable from the form package
- FormPropertyImpl
- all the FormType classes like BooleanFormType, DateFormType, EnumFormType, LongFormType, StringFormType …

i tried all these changes already and at least my example seems to work fine.

Re: DeployCmd (and other Commands) not Serializable

retourfer — Thu, 19 Jul 2012 12:52:23 GMT

Hi

i found some more classes which are not serializable. they are all located in the package org.activiti.engine.impl.persistence.entity. Some of them are serializable but unfortunately not all. I had a short look into some of them and they all have scalar attributes, Strings or references to other entities so i can not see any problem to make them serializable.

regards
Reto